Learn the deep parts without losing the plot.

Welcome to Loopy Pro!

Note: The manual is a living document. It is frequently updated in response to user feedback. If you have questions, please contact us via the support link found in Loopy Pro’s Help panel.

Be sure to go through the in-app tour (in the Help menu, top right button), and check out some of the fantastic tutorials already being released, and Max Yar’s excellent Loopy Pro course.

At its heart, Loopy Pro is a live-looper – it lets you record and layer pieces of sound which play in loops, to perform and construct musical arrangements on the fly. But it goes a lot further, and includes a variety of tools to customise your workflow so you can use Loopy Pro for a lot more than just live-looping.

Loopy Pro is:

• A live looper
• A sampler
• A MIDI sequencer
• A clip launcher
• A musical scratchpad
• A sequencer and arranger
• A mixer
• An Audio Unit host, supporting effects, synths, and MIDI sequencers
• An infinitely customisable control surface

And there’s a lot more still to come.

---

This guide will take you through the fundamental concepts behind Loopy Pro, starting with clips and the colour system, then effects and audio inputs, the actions system, widgets and the clock.

You’ll be introduced to the basics of live looping and the variety of ways it works in Loopy Pro, with concepts like pre-set vs free looping, Retrospective Record, Intro and Tail recording, and Overdubbing, and you’ll be introduced to the gestures system for on-screen interaction. For those who work with pre-made audio, rather than recording it live – or those who want to work with a combination of pre-recorded and live-recorded samples, this guide will also describe the many ways to bring audio into Loopy Pro.

Loopy Pro’s powerful mixer – where much of the project setup takes place – will be examined in detail, and each section and function described: colours, effects, audio inputs, MIDI and buses/sends. Then we will explore the Canvas, and how to set up almost any on-screen layout and control scheme you can imagine.

Song structure and sectioning, and the various ways this can be realised in Loopy Pro will be described, with Play Groups and the various configurations that can be applied. We will also explore the various Play actions that can be setup, for an additional level of customisation and flexibility.

We’ll go through Loopy Pro’s Actions system, and examine how it allows you to control every aspect of your project – with on-screen controls, or via a MIDI controller, or through Follow Actions. And we’ll follow with an examination of the MIDI Learn and MIDI Control system, and how to setup external MIDI controllers to control your Loopy Pro projects.

We’ll take a look at the sequencer, which has a DAW-like timeline for sequencing clip playback as well as driving a fully-automated live-looping session.

Finally, after a quick discussion of running Loopy Pro as an AUv3, hosted within another app, we’ll finish by taking a look at each settings screen.

But first, some Loopy Pro fundamentals:

Clips in Loopy Pro hold individual pieces of audio or MIDI. They come in two flavours: loops and one shots.

Loops usually appear as circles in Loopy Pro, and play their contents in a seamless loop. They are usually multiples of a bar in length. These are the building blocks of live-looping. Loop clips can be re-sized to be rectangular.

One shots, represented as squares or rectangles, play once and are usually shorter pieces of audio, like a drum hit, a vocal line, or a sound effect.

Audio clips (loops and one-shots) can be recorded live within Loopy Pro from the microphone, any audio hardware plugged into the device, and from any AUv3 Audio Unit Instrument, like a synthesiser.

MIDI clips can be recorded live, too, from the on-screen keyboard, a connected computer keyboard via Musical Typing, a connected MIDI controller like a keyboard or grid controller, or any plugin that generates MIDI like a sequencer. You can also create MIDI clips using the built in piano roll editor. MIDI clips record all MIDI they receive, including MPE data. Recorded MIDI notes can be edited in an easy-to-use piano roll. Non-note MIDI can be recorded and played back but is not yet editable.

You can even resample clips, audio or MIDI, which means recording some of Loopy Pro’s output back into a clip.

Clips play, stop, record and stop recording according to clip settings that can be set at the global, color or individual clip level. Swipe up on clips to see the clip details.

Clips as MIDI Destinations. Audio clips can be targeted by MIDI sources (MIDI clips, controllers, etc), in which case they behave as polyphonic samplers. Such clips can play the clip as pitched notes or as slices.

Clips can also be imported into Loopy Pro from outside: you can drag and drop from another app, like the Files app, straight onto a clip. You can import a clip from Files right from within Loopy Pro, or from Loopy Pro’s own Media manager. You can copy and paste audio from another app, or another device, or you can AirDrop from another device into Loopy Pro. You can also copy audio files over USB into Loopy Pro’s Documents folder, and open them from Loopy Pro’s Media manager.

Both imported clips and recorded ones can be time-scaled; when importing a clip, Loopy Pro will attempt to automatically identify the source audio’s tempo, and can optionally adjust the audio to match your current project.

Loops can be grouped together into sections, which can start and stop together, or play one at a time. Loops can be configured to play and stop with a count-in/count-out, which will wait until a given point in the timeline before starting or stopping, or they can play and stop immediately. Both loops and one shots can be configured to play only while holding, or to toggle with each tap – one shots will retrigger from the start, in this mode.

Clip States

A clip’s display indicates its state: whether it is playing*, stopped*, muted, recording, or in transition to playing, stopping or recording.

* Playing and Stopped

Playing and Stopped are terms we use when play-enabled and play-disabled or not-play-enabled might be more accurate. A loop is said to be playing if it is play-enabled and the transport is stopped; for the purpose of actions, it is in the play state or play-enabled state. If the transport were running, it would be playing. Similarly, when the transport stops, play-enabled clips are not said to be stopped. Why does this matter? Play and stop follow actions are triggered by clips changing between these states rather than whether the clip is actually playing or not. For example, if a clip is playing and the transport stops, Stop Clip follow actions aren’t triggered. Stop Clip follow actions get triggered when the clip switches from play-enabled to not play-enabled. That would be a lot of words to use; so, we say that the play-enabled clip is playing and the not-play-enabled clip is stopped.

In Loopy Pro, clips – both loops and one shots – are organised into colours. Colours provide a visual distinction between different kinds of clips in your project, but they also perform a larger role.

Colours in Loopy Pro behave similarly to tracks in a traditional DAW. Each colour has a channel strip in the mixer, with controls for volume, balance, mute, and solo, and you can apply insert effects and sends to the output of each colour. You can also specify a different output channel for each colour, if you are using an audio interface. And you can assign different audio inputs to different colours.

Colours aggregate the output of clips, and provide effects and audio routing. They’re like tracks in a traditional DAW.

Colours can also perform an additional role: customisation of behaviour. Clip Settings, which define how a clip plays and records, can be defined at three levels: (1) Project-wide; (2) at the colour level; and (3) at the individual clip level. For example, you can override the project-wide clip settings by changing some settings at the colour level – and then all clips of that colour will take on those settings.

With Loopy Pro’s flexible and powerful actions system, colours can do even more, and play a role in sectioning.

You can add as many colours as you like, in the colours editor. You’ll see a channel strip in the mixer for every colour associated with at least one clip in your project.

Most configuration in Loopy Pro can be defined at three levels:

1. Project-wide (global)
2. At the Colour level
3. At the Clip Level

The settings have the following hierarchy: all clips use the project-wide setting unless a setting has been overridden by the clip’s colour. In turn, a colour’s setting may be overridden at the individual clip level. If a setting is overriden at the colour or individual clip level, changes to that setting at the global level will not affect them. If a setting is overridden at the individual clip level, it is not affected by changes made at the global or colour level.

Individual actions can use settings that are independent of the inherited settings. For example, you could have an on-screen button or a MIDI Binding that triggers retrospective recording even if the inherited setting is normal recording. You might have a button that records with overdub as the After-Recording action even though the project-wide settings is Play after record.

This allows for a very flexible configuration scheme, where you can, for example:

• Designate a particular colour for Retrospective Recording,
• Nominate a single clip to be un-quantised and un-phase-locked,
• Use a particular button on a MIDI controller to perform a pre-set loop recording, while using free recording as default, or
• Configure an on-screen button to play a loop once and then stop.

See Clip Settings for more information about the configuration hierarchy and overrides.

Loopy Pro has a growing range of built-in audio effects, including a fully-featured stereo parametric equaliser, filters like low-pass and band-pass, reverb and dynamics, and also supports AUv3 Audio Unit effects.

Effects can be applied in a range of places. They can be applied as insert effects to colours, to audio inputs, and to the master output. They can be applied either pre- or post-fader, so that volume changes occur before or after an effect is applied.

Effects can be chained together, and the same effect can be applied to multiple tracks simultaneously, using Loopy Pro’s sophisticated automatic grouping and instancing features.

Loopy Pro also supports buses and sends: you can create a bus channel, which acts as an aggregator of multiple audio tracks, then apply effects to this bus. Then you can create sends from other channels, which allow you to determine how much of each channel is sent to that bus. This allows you to create sophisticated and expressive effects which are applied on top of each channel.

Once you have added effects using the mixer, effects will appear on the main screen of Loopy Pro in the bottom bar, or they can be hidden by tapping the eye icon on the toolbar of the effect window.

Loopy Pro allows you to record live audio from a range of sources. You can record from your iPad or iPhone’s built-in microphone, with an echo cancellation system to reduce echo and feedback from your speakers. If you have a USB audio interface, you can record audio from any number of its channels, including directing different channels to different colours.

You can also use AUv3 Audio Unit instruments and other generators within Loopy Pro, with sophisticated support for MIDI clips, MIDI controllers and AUv3 Audio Unit MIDI sequencers.

All audio inputs appear within Loopy Pro’s mixer as a channel strip. You can apply insert and send effects to any audio input, and configure each audio input to monitor through specified output channels, or even monitor through the target colour groups and associated effects, so that you can record the dry, un-effected signal while hearing the wet signal with effects applied.

Once you have added Audio Unit audio inputs using the mixer, they will appear on the main screen of Loopy Pro in the bottom bar, or they can be hidden by tapping the eye icon in the Audio Unit window’s toolbar.

Loopy Pro supports receiving MIDI from MIDI controller hardware, network and Bluetooth MIDI sources, and AUv3 Audio Unit MIDI generators, such as sequencers. You can also generate MIDI in-app with the On-Screen Keyboard or Musical Typing.

You can use MIDI to drive AUv3 Audio Unit instruments, to control Loopy Pro’s own actions via MIDI, and for recording to MIDI clips.

Like audio inputs, MIDI sources appear and can be configured in Loopy Pro’s mixer. You can chain MIDI sources together to apply MIDI filters, arpeggiators,  chord generators and the like.

Loopy Pro provides a powerful actions system for controlling every aspect of your project. Actions include controls for clip playback and recording, and audio parameters like volume, balance, pitch and speed. There are actions to adjust effect parameters and sends, play and stop the master clock, adjust input gain and enable/disable inputs, change tempo, and much more.

Loopy Pro’s actions can be controlled in a range of ways.

You can use MIDI Learn to easily make bindings between a MIDI controller and an action that corresponds to an on-screen object, such as a clip or a fader. You can make more sophisticated bindings to MIDI controllers manually using the MIDI Control screen.

You can attach actions to on-screen gestures, and to Follow Actions which occur in response to certain events, like clip playback or recording.

And you can control actions from on-screen controls that you can create called widgets.

Widgets in Loopy Pro are on-screen elements that you can create, arrange and configure to suit your workflow. There are buttons, sliders, dials, X-Y pads, text labels and even a clip slicer control, with more widget types to come.

Widgets work closely with Loopy Pro’s actions system: once you create a widget, you configure it to perform one or more actions. For example, a button widget could turn on a row of clips. A dial could adjust the levels of a few clips, or the amount of a send. An X-Y pad could control a number of effect parameters.

With widgets, you can create project layouts that work almost any way you can imagine.

To add a widget, access the  canvas editor and tap on the icon of the widget type you would like to create. Tap again to show the action editor.

See the Canvas section details about editing the canvas. See Actions for details about the available actions.

When you’re using Loopy Pro with no attached audio interface or headphones, Loopy Pro will by default enable its echo cancellation system. This is designed to reduce the amount of sound coming from your speakers that gets recorded. Without this, due to the proximity of the speaker and the microphone, it is very difficult to record loops without capturing all the audio currently being played.

Loopy Pro’s echo cancellation system requires a brief calibration, which involves emitting a series of chirps, and then performing some processing in order to determine the properties of your device’s acoustic feedback path. When you move your device around substantially – such as placing it down on a table – it’s recommended that you recalibrate the echo cancellation system to take into account the changed acoustic environment.

You can perform calibration at any time by opening the mixer and tapping the microphone icon at the top of the hardware input channel strip, then tapping “Calibrate”.

You can also disable echo cancellation in the same place.

Echo Cancellation Caveats

Disabling echo cancellation may be necessary if you wish to use a Bluetooth headset such as the AirPods, or if you are experiencing difficulties with audio level drops using screen recording.

Echo cancellation requires a built-in feature of iOS called “Measurement Mode”, which has a number of unfortunate quirks, including preventing the use of Bluetooth audio devices and dropping the device output audio level.

By disabling echo cancellation, you will also disable Measurement Mode, which will resolve these issues, at the cost of losing the echo cancellation functionality. I have been in discussions with the team at Apple and hope that these shortcomings will be resolved in time.

A Loopy Pro project contains layout pages, the project’s audio files and the project profiles that contain the MIDI mappings for that project. Loopy Pro projects can be opened and managed in Loopy Pro’s project browser and from the iOS Files app. You can use the iOS Files app to manage and backup your projects.

The canvas is Loopy Pro’s central area. It contains the clips and widgets with which you interact. Tapping the pencil icon lets you add, delete and re-arrange clips and widgets. You can add pages to your project while in canvas edit mode.

Control profiles store the MIDI and keyboard mappings we call bindings. There are two types of profiles:

• Project profiles which are stored in the project itself.
• Global profiles which are accessible from all projects and should not be used to target project-specific elements.

Control profiles are editable and can be accessed from the Control Settings panel. When you use MIDI Learn, the created bindings are stored in these profiles.

Loopy Pro is optimized for seamless real-time musical performance. It provides some tools to help you get the most out of your device.

IDLING

Loopy Pro features an idling mechanism that puts inactive plugins to sleep to free up the DSP (digital signal processing) resources they use. Effects that are receiving no signal are automatically idled as are Audio Unit Instruments whose channels are muted. This mechanism allows you to load more plugins than would normally be able to be loaded without taxing your device. When a plugin is idle, it will not respond to incoming MIDI. Turning an effect off also frees up the DSP resources that it uses.

Disable automatic idling. There are cases, such as when a sampler is loaded as an effect, where you may want to disable idling. You can long-press on the On/Off/Idle display in an AUv3’s window to disable idling for that plugin. When you disable idling for a plugin, Loopy Pro will disable automatic idling for all instances of that plugin and will apply the setting in other projects as well.

While idling frees up the DSP resources used by a plugin, idled plugins still use memory and may use non-DSP CPU resources. Some idled plugins may consume power and background resources even when idle.

DSP STATISTICS

Loopy Pro’s DSP % indicator provides a reading of the percentage of available DSP resources being used. This indicator is helpful for assessing your device’s current processor load. If the DSP load goes over 100%, audio artifacts such as crackles and pops are likely. Tap on the indicator to see a listing of the loaded plugins and the amount of DSP resources they are using.

To reduce the DSP load, you may want to do one or more of the following:

• Increase the buffer size in Loopy Pro’s System Settings panel
• Mute unused Audio Instruments
• Turn off unused effects
• Re-enable idling for any effects whose idling was turned off
• Eliminate unnecessary plugins
• Use buses rather than insert effects for effects used by more than one channel strip

Set Lists are lists of projects that can be used to switch between projects during a performance.

The clock in Loopy can be found at the top right, and controls both your session’s tempo, and the quantisation interval for certain actions, like recording loops – the “Master” cycle length. Tap on the tempo or where — (indicating no tempo has been set) is displayed to pop up the clock panel.

Tempo

You can adjust the tempo of your session by dragging the tempo jog wheel right or left, tapping in the left or right sides of the jog wheel, or tapping in the middle to enter a tempo using the keyboard. Your project’s audio will be time-scaled dynamically to fit the new tempo.

You can also tap out a tempo by tapping on the “Tap” button at the top left of the clock controls.

You can also synchronise the clock with other hardware and apps, using either MIDI Clock Sync or Ableton Link, and you can modify any clock parameters using actions and MIDI control.

Once you have audio content loaded within a project, you will see white bars on the tempo jog wheel which correspond to the native tempos for the loaded audio. The jog wheel will snap to these points, making it easy to return to the original, un-time-scaled audio at any point.

Tempo Correction

If your tempo has been set by the first recorded loop, sometimes it may be incorrectly guessed as double or half the actual tempo. You can use the ÷⨉ tempo correction control to the right of the tempo jog wheel to halve or multiply the tempo without time-scaling the loops.

Reset Tempo

You can reset the tempo to an “unset” state at any point. This will put Loopy Pro into a state ready to assign the tempo from the next loop which is recorded.

Detection Range

When the tempo is currently unset, you can provide minimum and maximum bounds for detection of tempo, when tempo is set by recording the first loop. This can help if a loop is detected at double or half the desired tempo.

Round to Closest BPM

This option is only available before the tempo has been set. Turn this option on to have Loopy Pro set the boundaries of the tempo-establishing first loop so that the tempo is set to the nearest whole number BPM. This can be useful when planning to export the recorded clips for further use within a DAW environment that may require whole-number tempo values. This option does not time fit the loop but rather adjusts its end point so that the loop’s tempo is an integer.

Master Cycle Length

In many traditional live-loopers, the first loop sets the length of subsequent loops. Loopy Pro provides additional flexibility, and allows you to dynamically set this “Master” length. If you are using Count In and Count Out for your record configuration – Loopy Pro’s default setup – it’s this which determines the length of your loops.

You can change this length via the clock controls by tapping the buttons beside the “Bars” indicator. Jump straight to a length by tapping the numbers, or vary the current length using the mathematical operators: Double, Halve, Add 1, Subtract 1.

You can also modify this length using actions and MIDI control.

Time Signature

You can set a wide range of time signatures in Loopy Pro by tapping the time signature button at the bottom right of the clock controls – by default, this will read “4/4”, indicating four quarter notes per bar. Loopy Pro lists common time signatures for you to choose from. The numerator (the top number) is the significant number in Loopy Pro. That is the number beats per measure. Loopy does not make use of the denominator (the bottom number). Time signatures displayed as 6/8 and 7/8 are the same to Loopy as 6/4 and 7/4.

If you enable the “Update Tempo” switch on this screen, Loopy Pro will keep the duration of each bar constant, while updating the tempo to fit the number of beats you have selected into that duration.

ADDITIONAL CLOCK SETTINGS

Tap on the gear icon to access additional clock settings.

Pause Clock When Idle

This is the same as the setting in the global Clip Settings. When no clips are playing, the clock will be paused.

Perform Count-In

Performs a one-measure count-in when the playback is started via the transport’s play button.

Reset Playhead on Stop

This determines whether the playhead is reset to the beginning when the transport stops. It can be set independently for the main screen and the Sequencer.

Metronome

Loopy Pro has a built-in metronome, both audio and on-screen flash, which you turn on and off using the metronome and flash buttons at the bottom left of the clock screen.

The metronome has four different sounds: A woodblock, high-hat, beeps, and clicks. You can adjust its volume, and if you have an audio interface, you can assign the output channels it is sent to, so that you can separate the metronome from other outputs.

You can also configure when the metronome is enabled: always, or only when a loop is counting-in to begin recording.

Loopy Pro is many things, but at its core it’s a live looper. Live looping is a form of live music production where a track is built up in layers, in real time. In a performance, it allows the audience to witness a song being built from scratch, often from nothing more than the performer’s voice, augmented by effects.

In the studio, looping provides a fun and creative way to experiment with musical ideas and can be an invaluable songwriting aid.

In most live looping environments, the first loop sets the tempo, and forms the basis for the rest of the session. Loopy Pro provides a number of ways to begin a session, but by default it will wait for your first loop.

Start and Stop Record

To record your first loop, you tap on one of the empty loops. Loopy Pro begins recording as soon as you release your finger, and will continue recording until you tap again – recording will finish when you release your finger.

Note that recording triggers upon release, rather than press, in order to achieve better touch and timing accuracy: touches on a touchscreen can often be missed if one’s fingertips are too damp or too dry. So: when you’re ready to begin recording, place a finger on the screen. Then release to begin. Ditto when finishing: place your finger on the screen head of time, then release to finish.

You can change this setting to on press, if you choose, by opening Clip Settings, then Gestures at the bottom, and turning on the switch beside “Record On Press”.

Automatic Loop Detection

Automatic Loop Detection allows Loopy Pro to help you record a tight first loop. It applies only to the first loop. This feature is primarily for people new to looping that can use some help establishing a tight first loop. It is optimized for a few conditions: the meter is correctly set, the input signal is sufficiently strong, the loop length is a power of 2 measures long (i.e. 1, 2, 4, 8 or 16 measures), the audio is reasonably percussive with a clear rhythm.

If you have trouble with automatic loop detection, make sure that you have a strong signal in Loopy Pro’s mixer and that your loop is an appropriate length as described above.

If you find that the detected loops are not the correct tempo, you can revise the detection range from the clock controls.

If you set a loop length and, optionally, an approximate tempo before recording, and enable the “Auto-End Detected Loop” setting in Clip Settings, Loopy will automatically stop recording when it detects a loop and begin playing, for a seamless automated start. NOTE: this feature works best when the loop length is a power of 2.

But as you gain experience with looping, you may choose to disable automatic loop detection and coordinate the record start and stop timing yourself. You can turn off automatic loop detection in Clip Settings, by turning off the switch beside “Auto Loop Detection”.

Timing

Without automatic loop detection on, the time that you start and stop recording the first loop is very important. You begin recording on the first beat – the “1”  – and then finish recording at the end of the last beat; the final “1”. For example, if you have a one-bar loop as your first loop – “1, 2, 3, 4” – you’d trigger record start on the first “1”, and end on the “1” after the end: “1, 2, 3, 4, 1“. Loopy Pro will then begin playing back your loop immediately.

Refining the First Loop

After the first loop is recorded, a glyph appears to its left. Tapping the glyph brings up a panel for refining the first loop. The glyph goes away when either the next loop is recorded or the project is saved. There are two different versions of the panel depending on whether auto loop detection is turned on or not.

If auto loop detection is on, the panel provides several proposals for the loop in addition to an option to trim the loop manually. Otherwise, the panel lets you refine the loop’s start and stop points, the tempo and the beats per bar.

Starting with a Pre-Set Tempo

You can also set the tempo prior to recording your first loop and optionally use a metronome to keep you in time.

Loopy Pro provides a variety of ways to record loops.

Pre-Set

With a pre-set length configuration, Loopy Pro will count in to the next cycle, then record for a set length and stop recording automatically. This works well if you know in advance how long you want your loops to be, and allows you to record hands-free without needing a foot controller.

This is the default configuration in Loopy Pro, and mimics the behaviour of many hardware loopers.

There are a number of ways to configure loops to use a pre-set length. From Clip Settings, turn on “Auto Count Out”, and set “Count In Quantization” and “Count Out Quantization”:

• Select Master use the clock’s master cycle length, which can be adjusted dynamically and is initially set by the first recorded loop.
• Select Custom to define a custom quantisation interval.

You can use a combination of Count In and Count Out settings, to change Loopy Pro’s behaviour. For example:

• Set “Count In Quantization” to Custom and 1 Bar to perform a 1 bar count-in, regardless of the master length, and then set “Count Out Quantization” to Master, to record for the master cycle length.
• Set “Count In Quantization” to Master and “Count Out Quantization” to 2 Bars to sync the beginning of a loop with the master cycle length, and record for 2 bars.

You can also define these settings at the Colour and at the Clip level, as well as for individual actions for triggering via a widget or a MIDI controller.

Finally, you can also pre-set the length of an individual clip in that clip’s detail screen, which will automatically stop recording after the given length.

Free

Loopy Pro also supports free looping. Upon starting a recording, Loopy Pro will continue recording indefinitely, until you trigger record end. The length of the loop will be – by default – quantised to the closest number of bars.

This allows you ignore any length restrictions, and determine the duration of each loop as you go.

To enable free looping, turn off the “Auto Count Out” setting from Clip Settings. You can also define this setting at the Colour and at the Clip level, as well as for individual actions for triggering via a widget or a MIDI controller.

You can optionally quantise the beginning and end of recording by setting the “Count In Quantization” and “Count Out Quantization” settings. This will cause Loopy Pro to count-in or count-out to sync with the given interval:

• None: Start/Stop recording immediately, regardless of position in the cycle
• Master: Start/Stop recording in sync with the master cycle length, which can be adjusted dynamically and is initially set by the first recorded loop.
• Custom: Define a custom quantisation interval

 

Retrospective Recording allows you to simply play, and then trigger a recording afterwards, when you have something you’d like to capture. This allows for a wonderfully free and creative workflow.

To enable Retrospective Record, open Clip Settings and turn on the switch beside “Retrospective Recording”. You can also define this setting at the Colour and at the Clip level, as well as for individual actions for triggering via a widget or a MIDI controller.

The duration of loops recorded via Retrospective Record is set by the master clock cycle, which can be changed on-screen or via an action, either from a button on-screen, or a MIDI controller.

Set “Retrospective Quantization” to determine how recording behaves:

• Immediate: Recording will capture the immediately-preceding audio, irrespective of the current position in the current clock cycle.
• Quantized: Recording will capture the whole preceding clock cycle, in sync with the cycle. If, for example, the current cycle is 2 bars and you trigger Retrospective Record at bar 1, beat 3 – i.e. shortly after the beginning of the cycle – Loopy Pro will record up to the end of the preceding bar; it will not capture the audio from the end of the last bar to the current position.

With Loopy Pro’s very customisable configuration system, you can designate individual colours or even individual loops to use Retrospective Record, while keeping the other loops in normal record mode. Or, you can nominate a particular on-screen button or MIDI controller button to initiate Retrospective Record.

Loops in Loopy Pro can have attached intro and tail/outro sections, which play before the loop begins, and after it ends, respectively. Tail sections can also be mixed into the loop, after the first cycle has been played.

You can enable “Record Intro” and “Record Tail” in Clip Settings, and these additional parts will be recorded.

Intro recording: Intros are made up of audio that happens during a count-in before the main loop starts recording. Intro sections are particularly useful for representing anacruses/up-beats: part of a musical phrase that precedes the first beat. During playback, the intro is played before the loop starts playback. It is not repeated as the clip loops.

During a recording count-in, Loopy Pro will listen for audio and record any audio played before the count-in’s end as the intro. When intro recording is on, a ‘waiting for threshold’ message will appear during the count-in. Intro recording starts when audio crosses a threshold to trigger the intro recording. For intro recording to work, there must be a recording count-in and threshold recording must be off in recording settings. Threshold recording interferes with the threshold used for intro detection.

Tail recording: After ending a loop recording, Loopy Pro will continue to record for a little while. Recording will stop when Loopy Pro detects the end of a decay, when the audio level is no longer decreasing. You can also tap to end tail recording immediately.

Tail sections allow you to capture the end of a reverb, or a natural acoustic decay, without it being cut-off at the end of the loop, for much more natural-sounding loops.

You can also designate regions of imported audio to be an intro or outro, in the import screen, or after import on the clip detail screen.

After a loop has been recorded, you can record additional layers on top of the same loop. This is overdubbing and you can use it to, for example, add harmony lines to a melody, or augment a beatbox loop with additional sounds.

While a loop is overdubbing, it will continue to add new layers for as long as recording continues.

There are a number of ways to trigger overdubbing. By default, you can 2-finger-tap a loop to immediately begin overdubbing, and tap again to end (you can change this gesture, if you like, in Clip Settings, to something like a swipe or tap). You can also trigger overdubbing via a “Record” action, from a button on-screen or a MIDI controller.

To automatically begin overdubbing after the first loop has been recorded, you can also set the “After Recording” setting in Clip Settings to “Overdub”. This setting can be assigned at the global level, for individual colours, or individual clips.

Loopy Pro has a number of built-in gestures which you can perform on-screen. You can configure these however you like, either at the global level, per-colour, or per-clip.

Here are the default gestures:

• Tap: Toggle a loop playing, or begin playing a one-shot. If the clip is empty, toggle record. Record will trigger upon release by default, in order to achieve better touch and timing accuracy, but this can be changed to on press if required from Clip Settings.
• Two-Finger Tap: Toggle overdub on a clip
• Swipe down/left/right: Clear a clip’s contents. Swipe further (long swipe) to clear immediately, bypassing the confirmation popover.
• Swipe up: Show the clip detail screen.
• Two-finger rotation/twist: Offset a loop
• One-finger circle within the loop’s perimeter: Instant volume adjust
• Hold-and-drag to another clip: Merge; place a second finger down at any time to copy, rather than move.

You can bind any actions to gestures, to create very custom interfaces. Available actions for binding are: tap, two-finger-tap, swipe (any direction), swipe up, swipe down, swipe left, swipe right, long swipe (any direction), long swipe up, long swipe down, long swipe left, long swipe right, long press.

Loopy Pro can be used as a live-looper, a clip-launcher, or a combination of the two. You can import pre-recorded audio or MIDI to clips, and then play them alongside live-looped content.

With Loopy Pro’s high-quality live time-stretching, you can import pre-recorded loops, then reset the clock tempo, putting Loopy Pro in a state ready to take the tempo from the next recorded loop.

The next loop that you record will behave like the first loop of the session. The tempo and master cycle length will be derived from that loop, and all other audio content in the project will be instantly and automatically time-scaled to fit that new tempo.

This is an incredibly powerful  way to run a traditional live-looping performance while also augmenting it with pre-recorded content – all without requiring a pre-set tempo.

Loopy Pro can load content into projects in almost any audio format, with time and pitch adjustments to fit. There are a wide range of ways you can load content into Loopy Pro:

Drag and Drop

You can drag-and-drop one or more files from any compatible app, such as Files, with its built-in support for services like Dropbox and Google Drive, and USB hard drive and network file server support.

By opening up Loopy and Files side-by-side using the iOS multitasking controls, you can simply drag audio files onto each loop, one at a time, or in a batch.

“Open In”

From any app that supports sharing, you can select Loopy Pro as the sharing target, and the audio will be loaded into Loopy Pro’s Media manager, ready for importing.

AirDrop

From a Mac or anther iOS device, you can AirDrop one or more audio files to your device running Loopy Pro, and then select Loopy Pro as the target. The audio will be loaded into Loopy Pro’s Media manager, ready for importing.

Files

Loopy Pro’s Documents folder is visible within the iOS Files app. You can copy and move audio files into this folder, and the audio will appear within Loopy Pro’s Media manager.

USB Transfer

Loopy Pro’s Documents folder is also available as a destination for copying files via a USB cable, using the macOS Finder, or a third-party app like iExplorer or iFunbox.

Clipboard

Loopy Pro can load audio files from the clipboard, copied either as files or using Audio Copy. You can find copied audio within Loopy’s Media manager.

Loopy Pro has its own media management system, accessed either by tapping the folder button at the top left of the screen, then “Media”, or by selecting the import button from the clip detail screen.

You can organise audio into folders, and import new audio from the document picker, or your music library (Note: Apple Music library is not supported, due to Apple’s DRM restrictions).

You can preview audio files by tapping the play buttons, or tap on the filename to open the import screen.

Import Screen

Once you have selected a file for import, the waveform is visible, with trim handles for selecting a subregion of the audio file. Drag these handles left or right, and pinch to zoom in the waveform area.

By default, if your project has a tempo set already, Loopy Pro will attempt to detect the tempo of the audio, and will apply time-stretching on import to fit the audio to your project’s tempo. You can specify the original tempo of the audio in this screen, and Loopy Pro will calculate the required time stretching parameters. Swipe left or right on the tempo jog wheel, or tap in the middle to type in a tempo.

You can also adjust the pitch of the imported audio, to fit the key of your project.

If you have selected a subregion of the audio file using the trim handles, Loopy Pro will offer to import the audio preceding and/or following the selected audio as intro or tail regions, which will play before and after the loop starts/stops.

Tap “Import”, and Loopy Pro will prompt for a target track, if you have opened the Media manager from the folder menu. If you are importing directly from the clip detail screen, the audio will be imported to the clip immediately.

After import, you can adjust the original tempo and further trim the audio, in the clip detail screen.

Loopy Pro’s powerful mixer gives you control over your project’s audio and MIDI inputs and outputs, effects, AUv3 and IAA instruments. Loopy’s mixer was designed to be flexible and to enable source/destination routing to be handled directly in the mixer.

In its simple form, you can adjust levels and balance, mute and solo for source and colour in your project. In its extended form, you can add audio and MIDI sources, add effects, add Audio Unit and IAA instruments, add buses, specify hardware outputs, set up audio and MIDI routing, and collapse mixer sections (which will become hidden when the mixer is in simple mode).

Open the mixer by tapping the   button from the main screen.

Adding to the Mixer

Add hardware inputs, Audio Unit Instruments, Inter-App Audio Inputs, and MIDI sources to your project by tapping when the mixer is open.

SIMPLE VS EXTENDED MODE

Loopy Pro’s mixer has two modes: simple mode and extended mode. Simple mode is a compact representation of the mixer that shows only the most essential controls with a reduced view of the main canvas displayed above it. Extended mode provides a complete display of the mixer and provides full-access to the routing options and channel configuration. When the extended mode is visible, tap to put the mixer into simple mode. When it is in simple mode, tap button to put the mixer into extended mode

SECTIONS AND ROWS

SECTIONS (COLUMN)

By default, Loopy Pro organizes the mixer’s channel strips into functional sections: (audio) inputs, MIDI  (hardware controllers and MIDI ports), MIDI Plugins, MIDI Colors, Colors (audio), Buses, and Outputs (currently Master channel). You can rearrange the channel strips by dragging them, as described in the Channel Strips section below.

These sections can be collapsed by tapping . Collapsed sections can be expanded by tapping . Collapsed sections are hidden when the mixer is in simple mode.

Showing collapsed items. You can tap on items in a collapsed section to show them without uncollapsing the entire section. Such items are given a white frame in the collapsed section display.

ROWS

The mixer has rows for: sources, pre-fader effects, post-fader effects, destinations and sends. Tapping on the  icon in a row cell (slot) lets you add an item to that row. Rows can be collapsed by tapping . Collapsed rows can be expanded by tapping . Collapsed rows can also be expanded by tapping in them. When a row is collapsed a dot indicates that the row cell contains an item.

The basic building-block in the mixer is the channel strip, a column in the mixer that might be:

• An audio input, such as a hardware input or an Audio Unit (AUv3) instrument
• A MIDI source, such as a MIDI keyboard an AUv3 MIDI sequencer
• An audio colour, aggregating one or more audio clips
• A MIDI colour, comprising one or more MIDI clips
• A bus
• The master output

Each channel strip has a fader and level meter, and mute/solo controls. Other cells (slots) are available in the channel strip depending on the channel strip’s type.

Audio channel strips. Channel strips for audio sources, audio colour channels and buses also have a balance knob and cells (slots) for sources, pre- and post-fader effects, send, knobs, and destinations. Hardware inputs, buses and the master channel do not have source cells.

MIDI. MIDI Channel strips have a destination cell (slot) and may have a source cell. While MIDI channel strips don’t have effects slots, you can chain MIDI plugins to create effect chains.

Renaming channel strips. To rename a hardware input, tap on its icon at the top of the mixer; tap the pencil icon next to its name and type the new name. To rename an Audio Unit instrument, open the AU’s window; tap on the gear icon and edit the name in the settings panel. To rename a bus, long press its name in the mixer and choose Rename from the popup.

Fine control. To adjust levels, balance or send amount, tap and swipe on that control. For finer control, tap and then move your finger away from the control: the control area will expand the further away you move from the original control location, giving you more control over fine adjustment.

Mute/Solo. The M and S letters at the bottom of channel strips, mutes or solos that mixer channel. Muting an Audio Unit instrument’s mixer channel will normally idle the instrument so that it uses next to no CPU resources. Muting an instrument will also idle the effects on the channel unless idling has been disabled for the instruments and/or effects.

Mute Position (audio channels only). By default, muting of audio input channels (hardware and audio unit inputs) is post-fader. By long-pressing the M button, you can move the mute position to Input which is the start of the signal chain. Typically, the mute position is only moved for hardware inputs. When the mute position is set to Input, muting the channel will idle the effects on the channel since the input level will drop to 0 (unless idling has been disabled for some plugins).

Channel Settings. Tap the icon at the top of each channel strip to access settings and controls for that channel, and long press to replace or delete.

Reordering channel strips. You can also reorder channel strips as you choose, by pressing on the icon at the top, then dragging left or right (or swiping up to remove that channel strip).

Master Output. Loopy Pro’s Master Output channel strip is somewhat unconventional. The controls and effects in the channel strip labeled Master apply to all hardware outputs. Note: a mixer update is planned to implement a more conventional architecture.

Channel Strip Signal Flow

 

Colours act like group buses for all the clips of the same colour. They aggregate the output of their clips and behave like tracks in a traditional DAW.  All  clips of the same colour get routed through the same mixer channel strip and share the same basic settings.

Each colour appears as a channel strip in the mixer, and has its own fader, balance, mute and solo, as well as sends, destinations, and effects (for audio colors). Audio and MIDI colours have their own channel strips. Both audio and midi colours inherit settings from the colour. The main menu’s Colour Groups item lets you set colour-specific settings, gestures and follow actions.

Tapping on a colour channel strip’s color icon, opens the Colour Group’s properties panel where you can set the properties for all clips of the colour.

If you have an audio interface, colours can be routed to any output channel.

Colours as destinations. By specifying a colour in the “destinations” section of a channel strip, clips of that colour will receive audio or MIDI from that source. This makes it simple to record (resample) from one color to another.

Audio and MIDI colour channel strips have the same rows (slots) as their underlying type: audio or MIDI.  Se the Audio and MIDI source section of this manual for more details.

Colour Management. By default, the mixer only shows colour channels for colours that have clips. If you would like colours to appear even if they have no clips, turn on Show Empty Colour Channels in Loopy Pro’s System Settings.

Adding colours. To add colours to the project, enter layout edit mode by pressing the and tapping on the paint bucket .

Loopy Pro can receive audio from the built-in microphone, an attached audio interface (with support for multi-channel input), an AUv3 Audio Unit or Inter-App Audio application. Each audio source has its own channel strip.

Audio source channel strips may have the following rows:

• Sources (only present for colour channels and Audio Units)
• Effects (pre-fader)
• Effects (post-fader)
• Destinations
• Sends

DESTINATIONS

The destinations cell shows where the audio is sent. All of the project’s colors and all available hardware destination are available. A source can be routed to any number of available destinations. The audio is sent post-fader. For pre-fader audio routing, use a send knob to send the audio to a bus.

ADDING SOURCES

Add audio sources to the mixer, by tapping  and choosing Add Hardware Input, Add Inter-App Audio Input, or Add Audio Unit Instrument.

MONITORING OPTIONS

Monitoring sends an input to an output such as the main output or headphones so that you can hear that input. When the internal mic and built-in speakers are used, monitoring is turned off by default to avoid feedback.

By default, when monitoring is on, it is done through the default output channels. But you can set any available output channels for monitoring and you may also monitor through colors. The Monitor Through selector let’s you choose available hardware outputs and/or colour.

Monitoring through colors. When you choose one or more colours for Monitor Through, the audio is sent through the effects chain of the selected colour or colours. When using monitor through colours, you should generally not monitor through a hardware output also if you want to hear only the effected signal. This allows you to “monitor wet, record dry”

 

 

Hardware inputs can be the built-in mic or inputs from an audio interface and are represented by a mic icon in the mixer. The default project has a single hardware audio input. If you are using Loopy Pro on a device without any equipment plugged in, this will be the built-in microphone. With an audio interface, this will be one of the available input channels provided by the audio interface.

Input Options. Tap the mic icon at the top of the channel strip to configure the hardware input. A number of different options may be available, depending on the connected hardware:

• Monitoring options
• Input Selection (if audio hardware is connected) – you can choose whether to use the audio interface input or the internal mic.
• Microphone Selection (if internal audio is being used) – the available built-in mics. The options depend on your particular device.
• Global Hardware Gain (only if device supports it)
• Echo Cancellation (internal mic only)
• Input Channels (audio interface only) – a choice of the device’s input channels.

Input Gain. As shown in the signal flow diagram in the Channel Strips section, there is an input gain stage between the actual hardware input and the pre-fader effects. Because this gain stage is so rarely needed (usually you adjust input levels on the audio interface itself), there is not an on-screen control for it in the mixer. You can control the input gain by adding a widget or MIDI binding. Use the audio source Adjust Parameter action, and choose the input gain parameter.

Global Hardware Gain. This setting is only available for some devices. It is a global setting that is applied by the hardware. The behavior depends on the audio interface itself. For some interfaces, this adjust the interfaces output gain. On some devices, it may also apply to input gain. It is a global control that applies to all channels.

You can have as many hardware audio sources as you like, including multiple instances of the same channel, so you can configure different effect chains on each one and mute or unmute duplicate channels as needed.

Loopy Pro supports hosting AUv3 Audio Unit instruments and generators, like synthesisers and other virtual instruments. These can be downloaded and installed from the App Store.

ADDING AN AUDIO UNIT INSTRUMENT

Add an Audio Unit instrument to your project by tapping when the mixer is open then choosing Add Audio Unit Instrument. Loopy Pro will present the New Audio Unit panel with all the available Audio Unit instruments. Normally, Loopy Pro will then pop up a list of MIDI Sources for playing the instrument. There is an option in the panel to turn off the MIDI Source prompt.

Turning the source prompt back on. If you have turned off the MIDI Source prompt, you can turn it back on by tapping the gear wheel icon in the New Audio Unit panel.

AUDIO UNIT USER INTERFACE

Tap the icon at the top of an Audio Unit’s channel strip or on the bottom bar to display its user interface in a moveable and resizable window. Tap or double-tap the titlebar to toggle fullscreen. Tap to close the window. Drag the bottom right handle to change the size of the window.

DOCKING

Audio Unit windows can be docked to the side or bottom of the screen. Tap to dock the plugin window to the side or bottom of the screen. Tap  to undock the audio unit interface.

AUDIO UNIT SETTINGS

Tap to access the audio unit settings panel. In the panel you can:

• Toggle the audio unit’s bottom-bar visibility.
• Adjust its gain (the mixer fader level).
• Edit the displayed name.
• Panic (turn off stuck notes)
• Turn monitoring on/off.
• Set the Monitor Through options
• Set the MIDI source and adjust MIDI settings such as range, transposition, MIDI filter and re-channelizing.
• Set the colour destinations.

PRESETS

Loopy Pro supports both factory presets (provided the Audio Unit) and user-created presets. Tap to open the presets screen, where you can select from the available presets. Any presets visible in the presets menu are available to Loopy Pro’s preset selection action. Long-press a user preset to rename it, and swipe left to delete. Tap on a preset to select it. The selected preset has a Save and Export preset beside.

Factory preset note. Many Audio Units have proprietary preset systems that do not expose their presets to hosts such as Loopy Pro. If you do not see the AUv3’s presets in Loopy Pro’s dropdown menu, you will have to add them to manually to Loopy Pro’s preset library by choosing New from the preset dropdown. For more on this topic see: https://wiki.loopypro.com/AUv3_Presets

MIDI SOURCES

Tap   to access MIDI Source options.

ON-SCREEN KEYBOARD

In the Audio Unit’s window, tap the button to show Loopy Pro’s onscreen keyboard. Keys tapped towards the upper side play at a lower velocity than when tapped towards the lower side. Tap to toggle hold of the current notes. Tap the to toggle position lock – when unlocked, you can pinch and zoom to navigate around the keyboard. Tap to expand the keyboard to fill the window, and tap to hide the keyboard.

MUSICAL TYPING

Tap to activate MIDI typing which lets you use a connected typing keyboard to play notes. The musical typing keyboard is added to the mixer as a MIDI source.

MIDI

Audio Unit instruments can be controlled with the on-screen keyboard or the Audio Unit’s own on-screen controls. Generally, they will be controlled by a MIDI controller or sequencer. Loopy Pro provides flexible MIDI routing.

There are a few ways to connect an Audio Unit to MIDI sources:

• Via the MIDI Sources panel that can be opened from the Audio Unit window by tapping
• Via the MIDI Sources options in the Audio Unit options panel
• By choosing a MIDI source in Loopy Pro’s mixer by tapping + in the Source row of the Audio Unit’s channel strip.
• By making the Audio Unit a destination of a MIDI source in Loopy Pro’s mixer.

BOTTOM BAR VISIBILITY

Audio Units will appear on the bottom bar on Loopy Pro’s main screen by default, for easy access. If you wish to hide an Audio Unit from this bar, tap  in the audio unit settings panel to toggle visibility.

IDLE MODE AND MUTING

By default, muting an Audio Unit Instrument’s mixer channel puts the instrument and the effects on the channel into Idle mode, where they use little processing resources. With Idle mode, you can have many different Audio Units loaded, without overtaxing your device’s processor. Tap the ON button, or mute it from the mixer or an action to put the Audio Unit into Idle mode. Tap IDLE or unmute the Audio Unit from the mixer or an action to re-activate it. When an Audio Unit instrument goes idle, the effects on the mixer channel will also go idle (since effects normally go idle when the incoming signal drops to 0) unless you have disabled idle mode for the effect.

If you wish the Audio Unit to remain active when muted, you can disable Idle mode by long-pressing on the IDLE button, then turning off the switch beside “Enable Idle Mode” on the popover that appears.

Loopy Pro has a growing collection of built-in effects, and also supports AUv3 Audio Unit effects which can be downloaded and installed from the App Store.

Tap the + button in the Effects section of a channel strip to choose and add an effect. The effect’s icon will appear on the channel strip. Tap to open the effect’s configuration, or double-tap to toggle the effect.

You can also move effects around by holding and dragging between sections on the same channel strip, or to different channel strips entirely.

To remove an effect, hold and drag it out of the Effects section or long-press and tap Delete.

Long-press on an effect in the Mixer to bring up the shortcut popup with options: Delete, Disable,   (toggle bottom-bar visibility).

SENDS VS INSERTS

Loopy Pro supports both insert and send effects. Insert effects are applied upon individual channels and affect the audio in situ. Send effects are sent to a bus, a sort of side-channel, and the output is sent to the bus destination. (See Buses and Sends)

When an insert effect is applied to an audio source, the affected audio will be recorded into clip. Insert effects can also be applied to colours, and will affect all audio output by the colour. Effects frequently used as inserts include filters and equalisers, distortion, chorus, limiters and compressors.

Send effects are applied on the output of a bus, to which channels (both audio sources and colours) may send a certain amount of their audio, set by a send knob. The affected audio is heard on top of the original audio stream coming from the original channels. Sends are often used for reverb and delay effects.

PRE VS POST FADER

Effects can be placed in pre– and post-fader positions. This describes the effect’s position in the signal flow, relative to the volume fader.

Pre-fader effects are applied before the volume fader is applied to the channel: they process the full-volume audio, and then that affected audio is passed into the volume fader.

Post-fader effects are applied after the volume fader: they act on the audio after the volume has been applied, and that affected audio is sent to the output as-is.

Whether you place an effect in the pre- or post-fader position depends on the effect in question. Distortion effects, for example, can behave quite differently with quiet audio versus full-volume audio, and you may want to place these in a pre-fader position to maintain tone at various volume levels. With reverb and delay effects, on the other hand, you may want these to ring out when adjusting the volume, rather than having their output reduced by the fader along with the rest of the channel’s audio, so these may be best placed in a post-fader position.

A performance consideration with pre- and post-fader positions: When you are using the same effect on more than one channel, it’s more efficient to place this effect in the post-fader position for all of the channels. This gives Loopy Pro the opportunity to internally group the channels together and use a single internal instance for the effect. In the pre-fader position, Loopy Pro must use separate internal instances for each channel.

EFFECT INSTANCES

You can use multiple independent instances of any effect, and each instance will be treated entirely separately, with its own configuration and interface. When you tap + to add an effect. The Add Effect popup appears. Any effect already used in the project appears at the top of the list with a letter label that identifies that effect instance.

Clones. When adding an effect, you can choose an existing instance from the top of the Effect popup to use a copy/clone of that instance as if it were the same instance. When you do this, the new instance will use the same letter as the previously existing instance. In the user interface, all instances that share the same letter are treated as if they were the same instance with a single configuration and single interface. These clones do not share audio input however. They process the audio sent to them in their respective chains.

The mechanism for these shared instances is a combination of intelligent internal routing – where channels are grouped together and a single effect instance applied to the group – and internal handling of multiple hidden instances. We sometimes refer to these clones as “an instance”, but they are generally clone instances of a plugin.

In most cases, Loopy Pro will create multiple, hidden instances of an effect, and automatically synchronise the state across all hidden instances, so that the effect appears as a single instance. There are rare cases where a single instance is used for all clones, but that only happens when the routing is such that all clones follow the same signal path to the output with no possibility of being separately routed.

If a cloned effect has a visual component that reflects the input signal (such as a spectrograph or meter), the metering may not reflect the signal going to the clone you are looking at. A single clone is internally marked as the ‘master’ and the visual displays the input to that clone.

See the performance consideration note above, concerning pre– and post fader positions.

IDLE EFFECTS

By default, effects which are disabled or have no input signal enter “Idle” mode, where they consume little processing resources. With Idle mode, you can have many different Audio Units loaded, without over-taxing your device’s processor. Tap the ON button, or disable the effect on the bottom bar of the main screen or with an action to put the Audio Unit into Idle mode. Tap IDLE or enable the effect from the bottom bar or an action to re-activate it.

If you wish the Audio Unit to remain active when disabled, you can disable Idle mode by long-pressing on the IDLE button, then turning off the switch beside “Enable Idle Mode” on the popover that appears.

EFFECT TAILS

When you turn an effect off, Loopy Pro will detect if there is a tail/decay – as with a reverb or a delay, for instance. When a tail is present, Loopy Pro will perform a smooth transition to avoid cutting off the tail: When you disable the effect, Loopy Pro will mute the effect’s input, then overlay the remaining tail on top of the dry, un-affected audio until the effect output becomes silent.

When this transition is happening, you will see the effect bar button/action flashing. Tap again to cancel this transition and immediately silence the tail.

BOTTOM BAR VISIBILITY

Effects will appear on the bottom bar on Loopy Pro’s main screen by default, for easy access. If you wish to hide an effect from this bar, tap from the effect’s configuration screen to toggle visibility.

Loopy Pro has a number of built-in effects. Here’s a list of the currently-provided effects, and some corresponding notes – see the roadmap for a list of other effects which will be coming soon.

• Reverb – A simple reverb plugin (Apple’s own AUReverb2), with a number of presets provided: Small Room, Medium Room, Large Room, Medium Hall, Large Hall, Plate, Medium Chamber, Large Chamber, Cathedral, Large Room 2, Medium Hall 2, Medium Hall 3, and Large Hall 2.
• Equalizer – A sophisticated parametric stereo EQ, with support for eight filter types: Peak, Band Shelf, Low-Pass, High-Pass, Band-Pass, Low Shelf, High Shelf and Notch. You can combine any number of these, and apply them to both audio channels, or just the left or right. To add a filter, begin dragging on the frequency response line; a peak filter will be created by default, and will follow your finger to allow you to shape the frequency response. Tap the circular handles for each filter to change the type, channel and parameters. All parameters can be controlled via actions; you can specify which parameters are available for control by tapping the “Parameters” item in the popover for each handle.
• Filters: Low-Pass, High-Pass, Band-Pass, Low Shelf, High Shelf – Single filters, based on the Equaliser.
• Dynamics – A combined compressor/limiter module (Apple’s AUDynamicsProcessor).

In addition to its built-in effects, Loopy Pro can load AUv3 effect plugins from the App Store.

AUDIO UNIT USER INTERFACE

Tap the icon of an effect, or tap the corresponding button on the bottom bar to display its user interface: This is displayed in a moveable and resizable window.

Tap or double-tap the titlebar to toggle fullscreen, and to close the window. Drag the bottom right handle to change the size of the window. Tap to dock the window to the side or bottom of the screen. Tap  to undock the audio unit interface.

PRESETS

Loopy Pro supports both factory and user presets for Audio Units. See Presets in Audio Units for details about Audio Unit Presets.

MIDI INPUT

Some Audio Unit effects support MIDI input. The Audio Unit window provides access to the same MIDI tools and options as Audio Unit instruments. See Audio Unit Inputs for details.

MIDI SENDING

Some effects, technically called music effects, may send MIDI as well as receive it. MIDI Guitar 2 is an example of a music effect. To send MIDI from an effect. First, add the effect on the audio channel strip that it will process. Then use the Add MIDI command in Loopy Pro’s mixer to add that effect instance as a MIDI source.

The mixer’s MIDI Channel Strips are for routing MIDI from MIDI sources to MIDI destinations. There are a few MIDI channel strip variants:

• External MIDI controllers and virtual MIDI ports – These are hardware controllers and virtual MIDI ports from other apps. MIDI input comes through these ports. They have no Source slot.
• MIDI colours – The output of MIDI clips or any MIDI directed to a colour.
• MIDI plugins – Any MIDI plugin that can send audio can be added to the mixer as a MIDI source

Loopy Pro supports full MIDI routing: you can send MIDI from a connected MIDI controller to one or more AUv3 Audio Unit synthesisers/virtual instruments, or drive an Audio Unit synthesiser from an Audio Unit MIDI sequencer. You can also send MIDI out to connected MIDI devices.

Sources. MIDI Colours and MIDI Plugins have a source row that displays the icons of the the channel’s MIDI. You can add a source to a MIDI channel by tapping on the + icon at the bottom of the sources slot. You can also add MIDI sources by tapping the mixer’s + icon and choosing Add MIDI.

Velocity Fader. The fader of a MIDI channel strip scales the note velocities of notes sent through the channel. This will only impact the note volume if the destination synth makes use of MIDI note velocity. Some synth or synth patches are not velocity-sensitive.

Destinations. MIDI Channel strips have two types of destinations: colours and non-colour MIDI destinations: audio clips, MIDI plugins, audio unit instruments, MIDI ports.

In the Destinations section on a MIDI channel strip, tap the + button to add a new destination – this will display a list of the loaded AUv3 Audio Units that can accept MIDI, as well as a list of the MIDI destinations available to the system.

DESTINATION OPTIONS

Tap a MIDI Destination (in destination slot) to open its settings.

Options:

• Enabled/Disabled – whether the destination is enabled to receive MIDI. This option is used when a controller has multiple MIDI destinations. You can disable or enable destinations so that only some of the destinations are active. The Enable/Disable MIDI Destination action provides a convenient way to switch which MIDI destination are active.
• MIDI Cables (not pictured) – if the MIDI Source is a MIDI AUv3 with multiple output cables, a MIDI Cables option will be available to choose the cable from which MIDI is received.
• Channel Filter – specify a channel filter, if any. If All channels is selected, all MIDI channels will be sent to the destination. If a particular MIDI channel is selected, only MIDI messages on that channel will be passed through. All other messages will be blocked.
• Range – specify the range of notes that will be passed through to the destination. Any currently playing notes are indicated on the Range keyboard
• Transpose – the amount by which to transpose notes being passed to the destination.
• Destination MIDI Channel – set a MIDI channel to which you want the notes remapped. All notes being passed through are mapped to this channel.

Different destinations of the same MIDI source can have different settings here, allowing you to split a MIDI keyboard out to different Audio Units, for instance.

MIDI Colour destinations have a a couple of options unique to MIDI colours:

• Monitor Through – When this option is on (the default), MIDI received by the colour is passed on to its destinations.
• Takeover – When this option is on, control messages coming in live will temporarily override control messages being played back by MIDI clips.

Use buses in Loopy Pro to implement effect sends, or to configure custom routing, such as sending the same colour channel to multiple audio interface channels at the same time.

You can add a new bus by either tapping the button then selecting “Add Bus”, or by adding a new send knob by tapping the + button within the Sends area of a channel strip and tapping “New Bus”.

Once a bus has been created, you can create any number of sends from channel strips to this bus, by tapping the + button within the Sends area of a channel strip.

Destinations. Buses can send their output to audio colours, hardware outputs or any other bus..

Sends appear as dials which you can adjust by swiping horizontally – make finer controls by moving your finger vertically away from the dial. You can also use actions to adjust sends from widgets or a MIDI controller.

Long press on a send dial to configure its position:

• Before All Effects – the audio from a channel strip will be sent to the bus before any effects or faders are applied.
• Before Fader – audio will be sent at full-volume, before the fader is applied, and after any pre-fader effects. This is the default.
• After Fader – audio will be sent immediately after the fader, and before any post-fader effects.
• After All Effects – audio will be sent at the end of the channel strip’s signal processing chain, after fader and all effects are applied.

Remove a send by long pressing and then tapping “Delete”.

In addition to changing the levels of whole colour groups, you can also adjust the levels of individual clips using the Clip Mixer. This can be useful for gain staging imported content, for instance, prior to applying the colour channel levels.

With the mixer in its simple mode, tap the  button to toggle the Clip Mixer.

You can also enter the Clip Mixer while the main mixer is hidden by long-pressing on the  button on the main screen. Tap it again to hide the Clip Mixer, or keep holding the button to switch to momentary mode, and the Clip Mixer will hide when you release the button, for quick changes.

With the Clip Mixer visible, swipe up or down on any clip to adjust the volume. While sliding, move your finger away horizontally to make finer changes. Swipe left or right to adjust the balance. Double-tap on a clip to set the volume back to 0 dB.

You can adjust multiple clips simultaneously by dragging a rectangle from any empty space over the clips you would like to adjust. Then swipe on any clip to adjust the group.

With the Clip Mixer hidden, you can also quickly adjust the gain of a single loop by dragging your finger in a circle around the perimeter of a loop; a momentary radial fader will appear. Move your finger around clockwise to increase the volume, and anti-clockwise to decrease. Let go to hide the fader.

The bottom bar on the main screen displays all the effects and audio inputs that you have added to your project.

You can enable and disable modules by tapping in the main area of each button, and you can expand the module’s interface by tapping the  icon – or double-tapping anywhere on the button.

You can also long press on these buttons to switch this behaviour around, so that a tap in the main area opens the module’s interface, and a tap on the ON/OFF button or double-tap will toggle the module.

Condensed Mode

As you add more effects and inputs, the bottom bar will expand upwards to fit the new items. You can switch the bar to condensed mode by swiping down on any of the buttons – each button will collapse down to a smaller form factor. Swipe up again to switch back to normal mode.

Hiding Effects and Inputs

You can also reduce the number of items that appear in the bottom bar by hiding items. Open an effect or source’s interface by tapping the   icon, then tap the icon to toggle hide. You can also choose to hide or show effects by long-pressing the effect in Loopy Pro’s mixer to bring up a popup that gives the option to hide or show the effect.

Making More Room

The buttons at the far left and right of the bottom bar can also be hidden by swiping them off the edge of the screen. Bring them back in by tapping the bar handle, or swiping them back in.

Open the clip detail screen by swiping up on a clip from the main screen, or from the canvas editor by tapping on a clip.

Here you can halve the length of the clip by tapping DIVIDE, and double it using EXTEND or MULTIPLY; Extend will pad with silence, and Multiply will repeat the clip’s contents.

You can import audio to the clip by tapping , and export the clip’s audio by tapping , and you can change the colour of the clip with the top right colour selector.

You can also rename the clip, by scrolling up to the edit field. The clip name will appear on the clip in the main screen.

If the clip is empty, you can define a pre-set length here, and the clip will automatically record for the set length.

Edit Button

Tap the edit button  to open the audio or MIDI editor pain as appropriate for the clip.

Trimming, Original Tempo and Intro/Outro

Adjust the start and end points of a clip using the start and end handles on the clip’s waveform. Pinch to zoom in and out. 

Fine adjustments. The trim handles will initially snap to beat boundaries when dragged. You can adjust the coarseness of the adjustment by dragging up or down (whichever is most convenient). If you vertically drag a little bit, you will be switched to coarse adjustment which is finer than the initial beat snapping. Drag farther vertically and you switch to fine adjustment. Text below the waveform indicates the current adjustment mode.

Scrubbing.  If your clip is not Phase Locked (see below), then you can tap and drag the playhead around to change the playback position.

If the audio has been imported, you can set the original tempo by either dragging the jog wheel, tapping the ÷ or ⨉ buttons, or tapping in the middle of the jog wheel and typing in the tempo. The clip will be time-stretched to fit your project’s tempo. If this is the first clip of your project, then your project’s tempo will be adjusted instead.

As you move the start and end points using the waveform handles, Loopy Pro will suggest a tempo that corresponds to a whole number of bars. Tap the suggestion to apply that as the clip’s original tempo.

If you inset the start or end point inwards, you can assign the preceding or following audio to be an intro or outro, respectively. These sections will play before or after the loop is started/stopped.

Parameters

You can also adjust the clip’s parameters: volume, balance, pitch, playback speed and rate, and overdub feedback.

Each of these parameters can also be defined at the colour level, and the parameters combine between levels. You can – for example – gain-stage each clip, but still modify the overall level and balance of all clips of the same colour (remember: colours are like tracks in a traditional DAW).

You can adjust any of these parameters via the Adjust Parameter action, for control with a MIDI controller, an on-screen widget or a Follow Action.

Speed and Rate

The “Speed” parameter determines how fast the track plays back, while keeping the pitch constant. When you adjust the speed, Loopy Pro will perform a high-quality time-stretch operation in the background, while playing the clip using a live time-stretch operation. When the time-stretch processing is complete, Loopy Pro will switch the new audio over.

The “Rate” parameter also determines how fast the clip plays, but the pitch of the clip will vary as you change the rate, just like tape or vinyl. You can use the rate parameter to reverse the track, by setting a negative rate, or tapping “Reverse”.

Like the other parameters, speed and rate are applied in addition to the settings at the colour-level – for example, if you specify a playback rate of 2.0x at the colour level, and 0.5x at the level of a particular clip, the clip will be played at 2.0 times 0.5: 1.0x.

When you adjust the playback speed or rate of a clip, Phase Lock (see below) will automatically be disabled, and the clip may go out of time with the rest of the project, as it’s playing at a different speed. You can turn on Phase Lock again and the clip will jump back to a synchronised position. You can also use the Phase Align action to perform this change, controlled by a MIDI controller, on-screen widget or Follow Action.

Overdub Feedback

Also known as “Decay”, this parameter defines how much of the current audio of a clip is carried over into the next overdub layer, while overdubbing.

Set to 0% to enter “replace” mode, where all existing loop audio is replaced by new audio. Set to 100%, the default, to mix all existing layers with new layers.

In Loopy Pro 2.0, Overdub Feedback applies only to audio clips.

Phase Lock

Here, you can set a loop to be either phase locked or free. A phase locked loop will lock its playback position to the main timeline, even when it is not playing. When you start a phase locked loop playing, it will begin playing at a position determined by the overall timeline. A free loop, on the other hand, will always play from the start, regardless of the current timeline position.

Loop/Play Once

You can define whether a loop will play continuously (Loop), or play once and stop (Play Once). This setting can also be defined for an individual action, for triggering by an on-screen button or a MIDI controller.

Playback and Recording Settings

You can override the clip settings, by turning on the switch beside “Playback Settings” or “Recording Settings” override. You can also open either the global- or colour-level clip settings from here, for convenience.

Follow Actions and Gestures

Set up clip Follow Actions in conjunction with Loopy Pro’s powerful actions system to perform actions when certain clip events occur, and to implement sidechaining with the Amplitude Envelope follow action.

You can also configure clip gestures here, which will override the global- and colour-level settings. You can configure the actions which are performed when you tap, two-finger tap, long press, or swipe or long swipe in any direction.

Audio clips (loops and one-shots) can be targeted from MIDI sources and played as polyphonic MPE rompler/samplers. The clips can be treated as pitched notes or slices.

To set up a clip as an instrument:

1. Tap + in a MIDI destination slot in Loopy Pro’s mixer.
2. Tap Play Audio Clip in the MIDI Destinations panel.
3. Use the clip picker to choose the playback type: Pitched Notes, Transient Slices, or Even Divisions.
4. Choose the clip you want to target.
5. Once the clip has been added to the mixer as a target, tap on it to show its destination options.

You can change the playback type in the destination options and set the pitch bend range. The default value is 2 semitones. Use 48 semitones when using an MPE controller.

Watch this quick tutorial.

Loopy Pro provides editors for audio and MIDI clips. To access a clip’s editor, click on the pencil icon in a clip’s details panel or use the Clip->Show Editor action. By default, the editor window is docked but can be made free-floating by tapping on .

Audio Editor

Loopy Pro’s audio editor is a streamlined non-destructive editor that provides the following functions:

• Move the clip’s start and and points
• Divide the clip in half
• Multiply (double) the clip’s length by duplicating the clip’s audio
• Multiply (double) the clip’s length by adding silence at the end
• Export the clip via the Share Sheet
• Import audio into the clip

MIDI Editor

The MIDI editor provides the same clip editing functions as the Audio Editor as well as a simple piano roll editor for editing recorded notes.

Piano Roll Editor

The piano roll currently provides note editing only. It is not yet possible to edit non-note MIDI data recorded in the clip. To edit non-note MIDI, export the clip for editing in another sequencer. Exporting a clip exports all the MIDI data as a MIDI file that can be opened in a more comprehensive MIDI editor. If your clip has note and non-note data in it, moving notes will not move the non-note events and will cause the note and non-note events to be out of sync.

These gestures are active in all modes:

• Pinch to zoom in or out in the editor.
• Two-finger drag to scroll the editing area.

Tools palette

• Pencil tool – When the pencil tool is active, simple note editing can be performed. Tap and drag in empty space to add a note. Tap an existing note to delete it. Long-press a note to select it. You can drag the handles at the beginning or end of the note to change its length, adjust its velocity from the popup or use the popup to delete, copy or cut.
• Select tool – When the select tool is active, tapping a note selects it. You can draw a selection rectangle to select multiple notes. A popup appears with options for Delete, Copy, Cut, Quantize, Velocity. Quantize will quantize notes to the current grid.
• Scroll tool – When the scroll tool is active, tap and drag to scroll the visible area. This tool is convenient for scrolling with out accidentally editing or selecting notes.

Grid Menu

When the grid is on, note placement and dragging is locked to grid points. Turn the grid off to have no grid restraints. The grid options are: Auto (zoom level dictates the grid points), eighths, triplets, sixteenths, 16th triplets, 32nds, 64ths, none

Loopy Pro’s canvas allows you to create your own project layout, with any number of loops, one shots, buttons, dials, sliders and other controls. With a rich system of actions, you can set up on-screen widgets to control every aspect of the session, on a variable-size canvas that can also be split over multiple different pages.

To access Loopy Pro’s canvas editor, tap the  button from the main screen. The grid will appear by default, accessed by the  button on the bottom toolbar.

On the grid, you can move and scale elements; select multiple elements at a time by dragging a rectangle from any blank space, and then move them as a group.

Copy elements by selecting them, then tapping “Copy”; paste them by tapping in a blank space, and then tapping “Paste”. You can copy and paste between projects, and even between different devices using iOS’s Universal Clipboard feature.

You can add rows or columns to the canvas by tapping the , etc. buttons, and remove them and their contents by tapping the  buttons.

Along the bottom of the canvas are the elements which can be added. Tap an element to add it to the canvas. The following sections describe the elements that can be added to the canvas, and their configuration.

Add audio clips – loops and one shots – to the canvas by tapping  or . Add MIDI clips by tapping or . MIDI objects generally have dotted lines.

Clips can be any size; loops will appear as rectangles if they are a non-square aspect.

Once a clip has been added, tap it to open the clip’s detail screen.

You can also assign colours and group clips.

Widgets are controls that you can add to your project layout, and configure to perform any number of actions to control the session. This allows for a very deep level of configurability and customisation – you can essentially make your own user interfaces using widgets.

Each widget type has a large number of action triggers associated with it; a button, for example, has Press, Release, Toggle, Double-Tap, Long Press, Two-Finger Tap, Swipe, and so on. A dial also has a Value Change trigger, in addition to Press, Release, Double-Tap and Two-Finger Tap. Each on-screen element, therefore, can trigger a large number of different actions depending on gesture, providing for very space-efficient control schemes.

You can define a single action per trigger, or a number of actions which can be performed in a sequence.

You can also trigger widgets via a MIDI controller, so you can mirror your on-screen layout on a MIDI controller of your choice. You can even trigger widgets from other widgets, to create complex functionality, and even libraries of functions.

Widgets can have labels (with support for emoji), as well as different colours.

State Feedback

Loopy Pro is equipped with a state feedback system that can keep widgets’ visual states in sync with the elements they control. For example, if you have a button that turns an effect on or off, the button will reflect the effect’s state even if a MIDI binding was used to toggle the effect.

Options. For some widget types, there are options to customize how state feedback works. In the widget edit panel, tap the gear wheel icon if there is one to set the options

• First Action – consider only the first action when determining the state.
• All Actions – consider all the actions when determining the state.
• Disabled – do not use state feedback at all.

For more details about how state feedback works see this wiki article.

The remainder of this section will describe the different types of widgets currently available. More widget types will be rolled out as Loopy Pro develops. (See the roadmap for details). See the available actions which can be triggered from widgets.

Buttons perform actions on press or release, as well as supporting a number of other gestures.

Create a button on the canvas with the  toolbar button in the canvas editor.

You can configure a button to, for example, enable an effect on press, and disable it on release, or set a send to 100% on press, and gradually ramp it back to 0% on release. Or you could set up a number of buttons to act as scene launchers, each set to trigger a particular set of clips. A button could perform a cross-fade between one set of clips and another, with a configured interval. Or you could set a button to load the next project in a set.

Buttons provide the following triggers:

• Press
• Release
• Hold/Release – for boolean actions
• Toggle – for boolean actions
• Double-Tap – note that double-tap actions will delay other taps, as the widget waits to see if any tap is a double-tap.
• Long Press
• Two-Finger Tap
• Swipe (any direction)
• Swipe Up
• Swipe Down
• Swipe Left
• Swipe Right
• Long Swipe (any direction)
• Long Swipe (Up)
• Long Swipe (Down)
• Long Swipe (Left)
• Long Swipe (Right)

Slider, dial and rotary encoder widgets perform continuous value actions as their values are adjusted. Their visual states update to reflect the underlying action values.

Adjust a slider or dial’s value by dragging up and down, or left and right for horizontal sliders. For finer control, move your finger away from the dial and use the virtual fader that appears.

Rotary encoders are adjusted by circular movements and can be used for relative adjustments such as clip offset and for sending relative MIDI.

Create dials on the canvas with the  toolbar button, and sliders with the  and buttons. Create rotary encoders with the button.

If the screen is narrow, the rotary encoder is not shown. Tap on the dial icon to pop up the dial/encoder selector when this is the case.

Horizontal and vertical sliders. Sliders are horizontal or vertical based on their aspect ratio. If a slider is wider than it is tall, it will be horizontal. If a slider is taller than it is wide, it will appear as a vertical slider.

These widgets provide the following triggers:

• Value Change
• Press
• Release
• Double-Tap – note that double-tap actions will delay other taps, as the widget waits to see if any tap is a double-tap.
• Two-Finger Tap

 

X-Y Pads give two-dimensional control over a pair of continuous value actions.

Create an X-Y pad by tapping the  button on the canvas editor toolbar.

Loopy Pro provides a configuration screen to map an X-Y pad to a loaded effect. Once you add an X-Y pad, its configuration allows you to choose an effect, and then select which parameters of the effect are controlled by each axis.

You can configure an X-Y pad to operate in two modes: Always On, or Hold. In Hold mode, the effect will be enabled on touch, and disabled upon release. You can tap the  button on the pad to lock or unlock the pad temporarily.

You can also customise an X-Y pad’s actions to perform any continuous action you like. You could, for example, use an X-Y pad to send a pair of MIDI CC messages to some external MIDI gear, or an AUv3 Audio Unit.

In custom mode, X-Y pads provide the following triggers:

• X-Value Change
• Y-Value Change
• Press
• Release
• Hold/Release – for boolean actions

The Clip Slicer/Button Grid is a special widget type – the first of many to come – that provides an interface for a specialised clip function.

Create a Clip Slicer/Button Grid by tapping the  button on the canvas editor toolbar.

Configure the Clip Slicer with an individual clip, and it will allow you to play individual slices of the clip using the pads, either divided by transients in the clip, or divided evenly across the clip.

You can configure the Clip Slicer for various sizes, from 4 pads up to 24; turn on or off Hold to Play, and customise the quantisation, so that segment playback is synchronised with the timeline.

You can also put the button grid into custom mode, and completely customise the behaviour of each pad. Each pad offers Press, Release, and Hold/Release triggers.

Radio Buttons and Stepped Dials are both versions of “List” widgets, which allow you to specify a number of different elements, each with associated actions, and switch between them. Radio Buttons are created from the Clip Slicer/Button Grid/Radio Button selector  in the canvas toolbar. Stepped Dials are created by tapping in the toolbar.

Radio Buttons and Stepped Dials are made up of selectable items that can be triggered by turning the dial or selecting a button. The currently selected item can be triggered by an action from another widget or a MIDI binding. Stepped Dials and Radio Buttons can be set to perform their actions on change or only when activated later by another widget, MIDI Binding or other action source.

Typically, the list items (the dial steps or individual radio buttons) are created one of two ways:

• manually by adding actions to the individual list items (dial steps or radio buttons0 OR
• automatically by choosing an Items Source (such as an Audio Unit’s presets) that fills in the list items

Important State Feedback Note! The state feedback setting discussed later in this section has a big impact on the behavior of Stepped Dials and Radio Buttons. Normally, these widgets adjust themselves to reflect the state of the actions and objects they control. Sometimes, this behavior is undesirable. When you want a dial or radio button’s active item to always reflect the last selected step, set State Feedback to Disabled in the widget’s settings .

Item Source + On Item Select

Use Item Source to use the list widget to fill its items using a select action such as Select Audio Unit Preset or the Send MIDI Message. Tap + to choose the action that will fill the list. When the select action is set up, the dial or radio button group will be set up with the number of buttons or steps needed and will feature appropriate labels.

On Item Select. The On Item Select actions are performed  when a list item is selected. These are useful for tasks such as enabling a synth or effect when one of its presets is selected.

Individual Items

Items (dial steps and radio buttons) can also be manually entered. An item can performs one or more actions when the item is triggered.

When an item is triggered all of its actions are performed. The image above shows a dial with 2 items that have one action in each item. Items can contain as many actions as needed.

Select/Deselect sub-items. Items can have Select, Deselect, or Select/Deselect actions. The actions in the select section are triggered when the item is selected. The Deselect items are triggered when a different item becomes selected. Different Select and Deselect actions are useful when something special needs to be done when switching away from the step.

Gestures (Stepped Dial only): Press, Release, Double-Tap, Two-Finger Tap

Settings

There are a few important settings that determine the widget’s behavior and appearance.

Perform Actions On (Option)

By default, when you press a radio button or change a dial selection, the item actions are performed immediately. There are options to customize the behavior. Access the options by tapping in the widget editor.

The options are:

• Change – Perform a step’s action as soon as the dial or radio button selection changes in response to user interaction or an action that targets the widget. When the selection changes due to state feedback, the selection’s actions are not triggered.
• Activation Trigger – Perform a dial step for radio buttons actions only when receiving an activation trigger or when double-tapped.
• Release (stepped dials only) – When manually turning a dial, only execute the action when releasing your finger. For example, you may use this option for a dial that changes presets. Rather than select each preset  you scroll through, it only selects a preset when you are done scrolling.

When Perform Action On Activation Trigger is turned on, selecting a dial step or radio button prepares the widget to act. The action isn’t executed when the step changes. It waits to be activated. The widget can be activated by double-tapping it OR by using an action which could be executed by another widget, a follow action or a MIDI binding. To trigger a stepped dial or radio button with an action, use the Trigger Widget action. Set the target to the widget you want to trigger. As the sub-action, choose Activate Current Value/Retrigger
.

Font Size

The font size used for the widget’s text.

State Feedback

When State Feedback is on, Loopy Pro will automatically adjust the selected step or radio button selection to reflect Loopy Pro’s state. For example, if you have a preset selector dial and change the preset without the dial, Loopy Pro will adjust the dial to reflect the current preset. Because the selection affects the widget’s behavior when triggered, it is important to make sure that this setting is set appropriately. In many cases, you will want this to Disable

The options are:

• First Action: the selection will be set to match the state of the first action of a step/radio button.
• All Actions: the selection will be set to match the state of all actions of a step/radio button.
• Disabled: the selection will not be changed based state information. Use this option whenever you want a list widget to only respond to user interaction or actions targeting the widget.

Labels allow you to add text to your project’s canvas. You can change the font size, weight and colour, and longer content will word-wrap, and scroll if the label widget is smaller than the text, which means you can also use labels for longer passages, such as lyrics or set lists.

Add a label to the canvas by tapping the  button on the canvas editor toolbar.

By default, labels are non-interactive and can be overlapped on top of other canvas elements without interfering with their function. But you can also add actions to label widgets, just like buttons.

Label widgets provide the same set of triggers as button widgets:

• Press
• Release
• Hold/Release – for boolean actions
• Toggle – for boolean actions
• Double-Tap – note that double-tap actions will delay other taps, as the widget waits to see if any tap is a double-tap.
• Long Press
• Two-Finger Tap
• Swipe (any direction)
• Swipe Up
• Swipe Down
• Swipe Left
• Swipe Right
• Long Swipe (any direction)
• Long Swipe (Up)
• Long Swipe (Down)
• Long Swipe (Left)
• Long Swipe (Right)

 

Tutorial widgets  allow you to create your own tutorial content. These can be displayed by default the first time a project is loaded, and can be chained together to create a multi-step walk-through of the project.

You can create any number of separate pages for your project, and switch between them using the page selector on the main screen, or via an action, from a button or MIDI controller.

When in the canvas editor ( button), you can create a new page by tapping the  on the page selector, or long press to determine how the new page should be created:

• Copy, to copy the current page elements to the new page.
• Copy With Content, to copy the current page elements, including clip content, to the new page.
• Blank Page to create a blank page.

After you make a selection, new pages will be created the same way until you make a different selection.

Long press on a page label in the selector to delete the page, or to rename it – you can use a single letter or number, or an emoji, to represent the page.

Reorder pages by pressing then dragging.

Pages can behave purely as an extension of the canvas, or as actual content containers. With page actions, you can switch all loops on a page on or off, or solo an individual page, to behave like scenes of clips.

Assign colours to clips using the Colour Editor by tapping the  button on the editor toolbar.

Select a colour from the colour swatch at the bottom, and then tap or drag your finger over tracks to assign that colour.

You can add new colours by tapping the  button to the right – these will automatically appear in the mixer. Loopy Pro will add new colours in an order that attempts to maintain the maximum visual distinction between colours, and will keep them ordered by hue.

Colours which have been assigned to clips will be displayed with a grey bar above the colour swatch; empty colours have no grey bar.

Long press on a colour swatch to delete that colour.

Colour Settings

Tap  on the selected colour swatch to edit the settings for that colour – you can access the same screen by opening the menu at the top right of the screen and tapping “Color Groups”.

Here, you can rename the colour and, just like the clip detail screen, edit the colour’s parameters: volume, balance, pitch and speed. You can override the global clip settings, by turning on the switch beside “Playback Settings” or “Recording Settings” override.

You can also set up clip Follow Actions in conjunction with Loopy Pro’s powerful actions system to perform actions when certain clip events occur, and to implement sidechaining with the Amplitude Envelope follow action.

And you can configure clip gestures here, which will override the global settings. You can configure the actions which are performed when you tap, two-finger tap, long press, or swipe or long swipe in any direction.

Loopy Pro provides a number of different ways to define groups of clips, for near limitless customisability in defining song structure.

Play Groups

Play Groups are the most straightforward grouping mechanism.

Create and configure Play Groups by opening the canvas editor by tapping the  from the main screen, then tapping the  button to open the Play Groups editor. Here, you can drag loops together, or drag a rectangle around a set of loops, in order to create groups.

Tap a loop that’s in a Play Group to open the settings for that group. You can configure a group so that starting or stopping any loop in the group will start or stop all the other loops, or so that only one loop in the group will play at a time.

You can make groups mutually exclusive with each other, so that starting one group will stop the others.

Actions

You can also create your own completely custom groupings by using actions.

For example, to create a clip/scene launcher layout where loops in rows play together, you could create a column of button widgets, each bound to a solo action, with the clips in each row targeted, and “All Loops” set as the Solo Context. You can see this configuration in the “8×8 Scenes” sample project provided with Loopy Pro.

You can also create button widgets bound to the play action, with an arbitrary selection of clips, to create any kind of sectioning you wish.

Follow Actions

You can also use clip play/stop Follow Actions to trigger play/stop actions on other clips whenever a clip is started or stopped.

Loopy Pro’s powerful actions system provides for endless customisation of project layouts, and deep control via MIDI controllers.

Everything in Loopy Pro can be accessed via actions, which you can attach to on-screen widgets, like buttons and dials, or bind to triggers on a MIDI controller. You can assign actions to gestures, or to Follow Actions.

Actions include controls for clip playback and recording, and audio parameters like volume, balance, pitch and speed. There are actions to adjust effect parameters and sends, play and stop the master clock, adjust input gain and enable/disable inputs, change tempo, and much more.

With actions and widgets, you can essentially make your own audio production apps within Loopy Pro – effortlessly – and with a MIDI controller you can build your own looping setups, to suit your individual style.

Copying/Duplication Actions. Long-press on an action to Duplicate or Copy the action. After copying an action, long press on a target’s section header to paste the copied action. Long-press on a section heading to copy all of the actions in the section.

Re-ordering actions. Wherever actions are found, there is a Reorder button that allows you to change action order by dragging.

Deleting actions. To delete an action, swipe left on the action to expose the Delete action button. This is the  standard iOS list item delete gesture.

Action Timing/Sequence

For impulse action types, an additional circle button control is shown to the left of each action. Tapping this will display the timing/sequence controls for the action.

• After Last – perform the action after the previous one has completed. This includes waiting for any count-in for playback/record actions, for instance.
• With Last – perform the action at the same time as the previous one (do not wait).
• Next Trigger – perform the action the next time the trigger occurs (e.g. the next button press).

Use the Delay/Quantization slider to set when the action occurs. Delay will cause the action to occur after the given delay; Quantization will cause the action to occur in sync with intervals of the given quantum. Use Quantization to perform an action on the beat, for instance. Note that, for example, an action with Quantisation set to 1 beat, which is invoked on a beat boundary already, will have no delay at all.

Delay/Quantization Time Units: In Loopy Pro 2.0, a choice of time units was added. Delays and quantization can be set in terms of musical time or absolute time. When you set the Delay/Quantization slider, beats or secs will appear indicating the time unit. Tap on beats or secs to switch units.

Actions come in a number of different types, and are suited to different purposes:

• Impulse actions are triggered once and have no state; they are used for things like clearing a clip, initiating a parameter value change, saving or restoring a value or triggering a scene. Some impulse actions have a sub-action choice: assign, nudge, toggle, save, restore.
• Boolean actions have an on/off state; they’re used for things like enabling/disabling an effect, or toggling mute for a channel.
• Continuous actions have a numeric value; they’re used for an effect parameter, or a volume fader, or a send knob.

Depending on the control, different actions will be available. A dial widget will allow you to bind continuous actions to it, and a button’s Press action, or a MIDI Controller Program Change trigger will only allow you to bind Impulse actions, while a button’s Hold/Release trigger will accept boolean actions.

Saving/Restoring Values With Actions: Actions with the word Adjustment in their name generally provide options to assign, nudge, restore, save, and toggle values. When using the Save and Restore options, there is also a slot number into which you can save and restore the value. Trigger Widget actions may also have Save/Restore options.

The remainder of this section will describe all the actions currently available within Loopy Pro. This list is likely to grow as Loopy Pro develops further.

Actions that operate on clips.

Clip Selection

Loopy Pro provides a set of “Select” actions which control on-screen selection of clips. Selected clips appear on-screen with a white dot, and can then be used as an action target, allowing you to use the same action on whatever clip is selected.  There are actions to select the next and previous tracks, in left-to-right, top-to-bottom order, as well as actions to select tracks to the left, or right, above, and below.

The select targets Next Clip, Previous Clip, Clip Above and Clip Below apply to the current page. If the currently selected clip is on another page, the selection will move to the current page. The selection actions wrap. Select Next Clip, for instance, will select the first clip if the currently selected clip is the last on the page.

Select None. There is not currently a select ‘none’ option. Once the select action has been used, there will always be a selected clip. You can select a clip on a different page, if you are not using selected clip as the target and don’t want to see the selection dot.

Targets

The following targets are supported by clip actions:

• Specific clip – One or more specific clips
• Next Tapped Clip – Loopy Pro will prompt you to tap a clip on-screen when triggering the action
• Last Tapped Clip – The last clip which was tapped on-screen, or selected via “Next Tapped Clip” OR the last clip that started or finished recording regardless of whether recording was initiated by an actual tap. Last Tapped clip is a very handy target for MIDI Bindings if you want to stop a currently recording clip without specifying the specific clip.
• Selected Clip – The clip which is selected (see “Clip Selection” above)
• All Clips – Every clip in the project
• Specific Color – All the clips in a specific color
• Next Selected Color – Prompts you to select a colour on-screen when triggering the action; action will then affect all clips in that colour
• Last Selected Color – The last colour that was selected
• Colour of Selected Clip – All the clips that have the same colour as the selected clip (see “Clip Selection” above)
• Color of Next Tapped Clip – Prompts you to select a clip on screen when triggering the action; action will then affect all clips with the same colour
• Color of Last Tapped Clip – All clips of the same colour as the last clip that was tapped on-screen or selected via “Next Tapped Clip”

Play/Stop

Start or stop a clip playing.

Parameters:

• Action – whether to toggle playback on/off, depending on current state; always play, or always stop
• Quantization – how to synchronise start/stop with the master timeline: Default, None, Master (synchronise with the master clock’s cycle), Loop (synchronise with a specific loop, context-dependent), Custom.
• Fade In/Out – whether to apply a volume ramp in or out
• Respect Play Groups – when acting on a clip that’s a member of a Play Group, whether to perform Play Group logic
• Loop vs Play Once – when acting on a loop, whether to start the loop playing continuously, or play through once, then stop
• Record If Empty – if a clip is empty when the action is triggered, whether to begin recording
• Record Setup – If Record If Empty enabled, defines the recording configuration

Solo

Stop other clips playing when a clip is started, with a configurable context defining which other clips will be stopped.

Parameters:

• Action – whether to toggle solo, depending on current state; always solo, or always un-solo
• Solo Context – the context that defines the other clips that will be stopped as part of the solo: Color, or All Loops. You can specify a list of clips, colours or play groups which are excluded from this operation.
• Quantization – how to synchronise start/stop with the master timeline: Default, None, Master (synchronise with the master clock’s cycle), Loop (synchronise with a specific loop, context-dependent), Custom.
• Fade In/Out – whether to apply a volume ramp in or out

Mute

Silence a clip’s audio output; clip may continue playing, but silently.

Parameters:

• Action – whether to toggle mute, depending on current state; always mute, or always un-mute
• Ramp – duration over which to mute/unmute; a fade will be applied over this duration

Record

Start or stop recording a clip.

Parameters:

• Action – whether to toggle recording, depending on current state; always start recording, or always stop recording
• Use Default Settings – whether to use the settings defined at the applicable level (clip, colour, or global), or override these settings
• If Clip Has Audio – what to do if the clip is already recorded: Do Nothing, Toggle Playback, Play If Stopped/Overdub If Playing, Overdub, Rerecord)
• Other settings – see the record section in Clip Settings for details.

Adjust Parameter

Adjust volume, balance, pitch, speed, rate, overdub feedback or input gain for one or more clips.

Parameters:

• Parameter – the parameter to adjust
• Action – if trigger is impulse, whether to assign a specific value, nudge the value by some amount, toggle between two values, save the current value into a save slot, restore a value saved in a save slot
• Value – if trigger is impulse, the value to assign/nudge
• Ramp – if trigger is impulse, duration over which to apply the change. A smooth ramp will be applied.
• Minimum Value – if trigger is continuous, the minimum value to assign, at the lower end of the  controller’s range
• Maximum Value – if trigger is continuous, the maximum value to assign, at the upper end of the  controller’s range
• Controller Input Start – if trigger is continuous, the incoming controller value to treat as the lower end of the range. Incoming values outside this range will be clipped to the given bounds.
• Controller Input End – if trigger is continuous, the incoming controller value to treat as the upper end of the range.

Adjust Playhead

Move through the clip, either continuously via a continuous input like a slider, jump to a specific position or nudge back/forward through the clip.

• Action – if trigger is impulse, whether to assign a specific value, nudge the value by some amount, toggle between two values, save the current value into a save slot, restore a value saved in a save slot

Clear Clip

Clear all audio content from a clip.

Parameters:

• If Recording – What to do if the clip is currently recording: Stop Recording only, or Clear Clip.

Merge/Move

Copy or move the audio content from one clip to another, mixing audio with the destination clip

Parameters:

• Clear Source After Merge – Whether to clear the source clip once merge has completed (i.e. move, rather than copy)
• Play Target – Whether to start the target clip playing, if it is stopped

Multiply Clip Length

Extend the length of the clip by a factor of two.

Parameters:

• Pad with Silence – whether to extend the clip by padding with silence, instead of repeating the clip’s audio

Divide Clip Length

Truncate the length of the clip by a factor of two.

Show Detail Screen

Open the clip’s detail screen.

Show Editor (2.0)

Show the audio or midi editor of the targeted clip.

Select

Select a clip (see “Clip Selection” above).

Phase Align Clip

Realign a clip’s playhead to be in synch with the other clips and the clock. This action is necessary when changing a clip’s speed/rate since such changes generally put a clip out of alignment with the other clips and clock. It can also restore a clip to being phase-locked which is necessary after a speed/rate change since such changes will turn off phase-lock. This action is also useful with free loops when reversing a clip in order to realign it with the clock.

You can specify:

• Set Phase Lock – whether Phase Lock will be turned on for the clip
• Phase Quantum – if Set Phase Lock is disabled, specify a custom time quantum to sync to. For example, set “Whole Loop Duration” to sync with a time period equal to the length of this clip, so that it’s in sync with all other clips of the same length. Or, set it to 1 Bar, to sync to just 1 Bar intervals. The shorter the interval, the less travel the clip may need to perform to reach a synchronised position.
• Transition – whether, and how, to perform a smooth transition to the new playback position. “None” will disable any transition, so that the clip jumps to the new position instantly. “Constant Pitch Speed Up/Slow Down” will speed up or slow down the clip over the specified duration, while keeping pitch constant. “Variable Pitch Speed Up/Slow Down” will speed up or slow down the playback rate, with a variable pitch like a type/vinyl effect.
• Reset Rate – whether to reset the playback rate to a final value
• Final Playback Rate – the final speed/rate to assign

Offset Clip (2.0)

This action shifts offsets (“rotates”) a clip’s audio. When used with an impulse action (a button widget or other impulse-type event), the clip is rotated so that the old start point aligns with the clock position at the time that the action is executed. As a continuous action (such as from a fader, dial or rotary encoder), shift the start point by an amount determined by the controller/widget.

For example, if you have a recording of a quarter note count “1 2 3 4” and execute the action on beat 3, the clip gets rotated so that “1” now happens on beat 3. The new clip will be “3 4 1 2”.

Parameters (continuous mode only):

• Relative Control Speed – this controls the fineness/coarseness of the offset adjustment
• Quantization – whether the adjustments are quantized

Reverse Clip

Immediately Reverse the clip’s playback direction. This is the same as multiplying the Rate by -1. If a loop is phase-locked, the Reset Phase option will adjust the clip phase to remain clock-aligned which may require the playhead to jump.

Action: Toggle, Reverse, Forward

Option: Reset Phase. If a loop is phase-locked, the playhead will jump to stay aligned with the clock.

Phase-Aligned Reverse for Free Loops

To perform phase-aligned reverse with a free loop, do not use the Reset Phase option. Immediately after the Reverse Clip action, use the Phase Align Clip action with the following settings:

• Phase Quantum: Whole Loop Duration
• Transition: Rate (Variable Pitch)
• Transition time: > 1 ms (1 ms usually works but in some cases you may need it a bit higher)
• Reset Rate: Off

 

Peel/Replace Layers

Remove the top overdub layers of a clip, or replace them. This behaves a little like undo/redo for a particular clip.

Parameters/Options:

• Layer Count – number of layers to remove/replace
• Individual cycles (new in 2.0) – when this is on peel/replace individual loop cycles rather than an entire overdub (which might be longer than one loop cycle)

Cancel Count Ins/Outs

Cancel any recording or playback count-ins or count-outs that are in progress. This applies to all clips in a project.

Assign Clip Settings (2.0)

Assign new playback and recording settings. You can assign/override any or all clip settings. Exactly how the assigned settings are applied depends on the target. Assign Clip Settings works the same as if you performed the changes manually by changing global, color or individual clip settings.

All Clips

When the target is All Clips, the chosen settings become the global clip settings seen when you choose Clip Settings from the main menu. When assigning to All Clips, the new settings do not change any settings overridden at the color or individual clip levels. Assigning settings to All Clips does not change any settings overrides performed at the individual clip level.

Color

If a color is the chosen target, the chosen overrides will be added to setting overrides of the color.

Individual Clips

If the target is a specific clip or clips, the settings are assigned as overrides of the settings inherited from the global and color settings. When settings are overridden at the individual level, those settings are not influenced by any changes to those settings at the global or color level. To change the override settings, you must change them at the clip level. Targeting All Clip, does not remove or change settings made at the individual level.

Actions that operate on colours.

Play/Stop

See Clip Play/Stop, above.

Solo

See Clip Solo, above. Note that this action operates on the clips of this colour, and starts/stops the clips as required. This is a different action from Mixer Solo below, which operates on the mixer channel strip.

Mixer Solo

Solo or unsolo the colour channel in the mixer.

Parameters:

• Action – Whether to solo/un-solo based on current state; always solo, or always un-solo

Mute

Mute the output of a colour.

Parameters:

• Action – Whether to mute/unmute based on current state; always mute, or always unmute

Adjust Parameter

See Clip Adjust Parameter, above.

Play/Stop

This is the same as the clip Play/Stop action. It was added as a convenience as it simplifies selecting a play group since there are no other options.

Set Play Group Mode

This action lets you change a play group’s mode. The modes are: all clips play/stop together, one loop at a time, loops play independently.

• Target: Specific Play Group, Play Group of Selected Clip, Play Group of Next Tapped Clip, Play Group of Last Tapped Clip
• Assign/Switch: whether to assign a specific mode or  to switch between the enabled modes.
• Modes: All Clips, Single Clip, Independent

Enable/Disable Effect

Toggles the effect on or off. When off, the effect is bypassed.

Parameters:

• Action – Whether to enable/disable based on current state (toggle); always enable, or always disable.

Adjust Effect Parameter

Adjust a parameter value.

Parameters:

• Target – the effect parameter to adjust
• Action – if trigger is impulse, whether to assign a specific value, nudge the value by some amount, toggle between two values, save the current value into a save slot, restore a value saved in a save slot
• Value – if trigger is impulse, the value to assign/nudge
• Ramp – if trigger is impulse, duration over which to apply the change. A smooth ramp will be applied.
• Minimum Value – if trigger is continuous, the minimum value to assign, at the lower end of the  controller’s range
• Maximum Value – if trigger is continuous, the maximum value to assign, at the upper end of the  controller’s range
• Controller Input Start – if trigger is continuous, the incoming controller value to treat as the lower end of the range. Incoming values outside this range will be clipped to the given bounds.
• Controller Input End – if trigger is continuous, the incoming controller value to treat as the upper end of the range.

Select Effect Preset

Load a saved preset for an effect. Presets can be provided by the effect manufacturer, or user presets you create.

Open Effect Interface

Show the user interface for the effect. If the effect is built-in or AUv3, opens a window to reveal the effect. If the effect is an Inter-App Audio app, switches to that app.

Parameters:

• Action – Whether to show/hide UI based on current state (toggle); show, or hide. Note that “hide” only applies to non-IAA effects.

Mute/Unmute

Mutes or unmutes the source, with an optional ramp for a smooth fade in/out.

Parameters:

• Action – whether to toggle mute on/off, depending on current state; always mute, or always unmute
• Mute Position – where to apply the mute: Post-Fader, at the end of the signal chain (default), or Input, at the very start of the signal chain before any effects are applied. This can be useful to enable pre-fader effects to move into idle mode when muted.
• Invert Value – whether to invert the displayed state (e.g. show a button lit up when unmuted, rather than muted)
• Ramp – duration over which to apply a smooth fade

Solo

Soloes the source, muting all other channels.

Parameters:

• Action – whether to toggle solo on/off, depending on current state; always solo, or always un-solo
• Context – the solo context: Audio/MIDI Inputs Only, which will cause only other inputs to be muted while solo is active (default), or All Channels, which will cause all channels, including buses and color groups, to mute.

Adjust Parameter

Adjust gain, input gain or balance. Input gain is gain applied before the signal reaches the mixer. Input gain is primarily used to adjust the input level received from hardware inputs to simplify matching input levels.

Parameters:

• Parameter – the parameter to adjust
• Action – if trigger is impulse, whether to assign a specific value, nudge the value by some amount, toggle between two values, save the current value into a save slot, restore a value saved in a save slot
• Value – if trigger is impulse, the value to assign/nudge
• Ramp – if trigger is impulse, duration over which to apply the change. A smooth ramp will be applied.
• Minimum Value – if trigger is continuous, the minimum value to assign, at the lower end of the  controller’s range
• Maximum Value – if trigger is continuous, the maximum value to assign, at the upper end of the  controller’s range
• Controller Input Start – if trigger is continuous, the incoming controller value to treat as the lower end of the range. Incoming values outside this range will be clipped to the given bounds.
• Controller Input End – if trigger is continuous, the incoming controller value to treat as the upper end of the range.

Enable/Disable MIDI Destination [MIDI only | 2.0]

Enable, disable, switch or toggle a MIDI destination. Use this action to control which possible MIDI destinations are enabled for a MIDI controller. This action allows you to have multiple possible destinations of a controller and enable particular destinations without the need for multiple channel strips

Parameters:

• Target – a list of available MIDI destinations.
• Action – Toggle, Enable, Disable, Switch. When Switch is chosen, the targeted destination is enabled and all other MIDI destinations of the MIDI source will be disabled.
• Option – Invert Action. When the action is Toggle, inverting the value causes the Disabled state to be the ‘true’ state for the sake of state feedback.

Open Audio Unit Interface

Show or hide an Audio Unit plugin window.

Adjust Audio Unit Parameter

Adjust a parameter for an Audio Unit plugin.

Parameters:

• Parameter – the parameter to adjust
• Action – if trigger is impulse, whether to assign a specific value, nudge the value by some amount, toggle between two values, save the current value into a save slot, restore a value saved in a save slot
• Value – if trigger is impulse, the value to assign/nudge
• Ramp – if trigger is impulse, duration over which to apply the change. A smooth ramp will be applied.
• Minimum Value – if trigger is continuous, the minimum value to assign, at the lower end of the  controller’s range
• Maximum Value – if trigger is continuous, the maximum value to assign, at the upper end of the  controller’s range
• Controller Input Start – if trigger is continuous, the incoming controller value to treat as the lower end of the range. Incoming values outside this range will be clipped to the given bounds.
• Controller Input End – if trigger is continuous, the incoming controller value to treat as the upper end of the range.

Select Audio Unit Preset

Activate a preset for an Audio Unit plugin.

Open MIDI Keyboard [MIDI ONLY 2.0]

Open a Loopy Pro on-screen keyboard widget. Use this to open any Loopy Pro on-screen keyboards available in the mixer.

Parameters:

• Target – one of the project’s keyboard widgets
• Action – toggle, open, close

Mute/Unmute

Mutes or unmutes the bus, with an optional ramp for a smooth fade in/out.

Parameters:

• Action – whether to toggle mute on/off, depending on current state; always mute, or always unmute
• Invert Value – whether to invert the displayed state (e.g. show a button lit up when unmuted, rather than muted)
• Ramp – duration over which to apply a smooth fade

Solo

Soloes the bus, muting all other channels.

Parameters:

• Action – whether to toggle solo on/off, depending on current state; always solo, or always un-solo
• Context – the solo context: Buses Only, which will cause only other buses to be muted while solo is active (default), or All Channels, which will cause all channels, including audio sources and color groups, to mute.

Adjust Parameter

Adjust gain or balance.

Parameters:

• Parameter – the parameter to adjust
• Action – if trigger is impulse, whether to assign a specific value, nudge the value by some amount, toggle between two values, save the current value into a save slot, restore a value saved in a save slot
• Value – if trigger is impulse, the value to assign/nudge
• Ramp – if trigger is impulse, duration over which to apply the change. A smooth ramp will be applied.
• Minimum Value – if trigger is continuous, the minimum value to assign, at the lower end of the  controller’s range
• Maximum Value – if trigger is continuous, the maximum value to assign, at the upper end of the  controller’s range
• Controller Input Start – if trigger is continuous, the incoming controller value to treat as the lower end of the range. Incoming values outside this range will be clipped to the given bounds.
• Controller Input End – if trigger is continuous, the incoming controller value to treat as the upper end of the range.

Trigger Widget

Activate a widget’s functions.

Parameters:

• Action: The specific action of the widget to perform (e.g. Value Change, Press, Release, Double-Tap, etc.)
• Adjustment: For Value Change actions, the kind of adjustment to make: Assign, Toggle, or Nudge Value, or for continuous controls, Adjust Continuously
• Ramp – if trigger is impulse and action is Value Change, duration over which to apply the change. A smooth ramp will be applied.
• Minimum Value – if trigger is continuous, the minimum value to assign, at the lower end of the  controller’s range
• Maximum Value – if trigger is continuous, the maximum value to assign, at the upper end of the  controller’s range
• Controller Input Start – if trigger is continuous, the incoming controller value to treat as the lower end of the range. Incoming values outside this range will be clipped to the given bounds.
• Controller Input End – if trigger is continuous, the incoming controller value to treat as the upper end of the range.

Switch Page

Switch to another page.

Parameters:

• Action – The kind of switch to perform:
  • Show: Show the page, without playing or stopping anything
  • Switch: Stop playing the current page, switch and start playing the new one
  • Solo: Toggle solo of the page: stops playing all loops from other pages
  • Start: Start playing loops in the page
  • Stop: Stop playing loops in the page
• Target – The page to act on: Next Page, Previous Page, or a specific page.
• Quantization – How to synchronise start/stop with the master timeline: None, Master (synchronise with the master clock’s cycle), Loop (synchronise with a specific loop, context-dependent), Custom.

Copy Page

Copy the layout and optionally content of the current page to a new page.

Parameters:

• Source – The copy source: Current Page, Next Page, Previous Page, or a specific page.
• Copy Clip Content – Whether to copy contents of the clips to the new page.

Toggle Clock Pause

Toggle, pause or unpause the timeline.

Parameters:

• Reset Timeline After Pause – Whether to move the playhead back to zero after pausing (on by default).
• Perform Count-In – When unpausing from the start of the timeline, whether to perform a count-in with metronome prior to playback.

Seek Timeline

Move the sequencer timeline’s playhead. The position can be determined in terms of bars or sections.

A section is a timeline region where all the events remain unchanged as illustrated below.

Parameters:

• Absolute/Relative – whether to move the playhead to an absolute position or to move it relative to the current position
• Bars/Sections – whether the position slider is interpreted as musical bars (measures) or sections.
• Position – slider for choosing the timeline section or bar number.

Phase Align Clock

Reset Loopy’s clock position. Typically, this action is used with free loops to allow the clock to be re-aligned when switching between loops of different lengths if you need the loops to be lined up with the master cycle.

Phase-Locked Loops! Phase-locked clips will be offset (rotated) to stay aligned with the new clock phase when you use Phase Align Clock. Use this action with care when there are phase-locked loops in your project.

In Loopy Pro 1.x, the clock is reset to the start of the master cycle.

Parameters (to be available in 2.0):

• Master – Reset to the start (top) of the master cycle.
• Custom – Align the clock to a custom interval.

Tap Tempo

Update the tempo by tapping out a new one (for impulse triggers only).

Correct Tempo (2.0)

Halve or double the tempo without affecting clip playback. This action is equivalent to manually triggering the Tempo Correction options available in the clock settings panel.

Adjust Tempo

Modify the current tempo.

Parameters:

• Action – if trigger is impulse, whether to assign a specific value, or nudge the value by some amount
• Value – if trigger is impulse, the value to assign/nudge
• Ramp – if trigger is impulse, duration over which to apply the change. A smooth ramp will be applied.
• Minimum Value – if trigger is continuous, the minimum value to assign, at the lower end of the  controller’s range
• Maximum Value – if trigger is continuous, the maximum value to assign, at the upper end of the  controller’s range
• Controller Input Start – if trigger is continuous, the incoming controller value to treat as the lower end of the range. Incoming values outside this range will be clipped to the given bounds.
• Controller Input End – if trigger is continuous, the incoming controller value to treat as the upper end of the range.

Adjust Beats Per Bar

Change the current time signature with an option to keep the bar duration. Note that Loopy Pro time signatures are beats-per-measure. Loopy does not consider the denominator of a time signature. (I.e. 7/8 and 7/4 are the same.)

Action: Assign, Toggle, Nudge, Save. Restore

Parameters:

• Value – the number of beats per bar
• Update Tempo – Keep bar duration constant

Reset Clock

Stop playback, reset the tempo and master length to an unset state. The next recorded loop will define the tempo and master length.

Set Master Length

Assign the clock master length.

Parameters:

• Action – double, halve, or set a specific value.

Toggle Metronome

Turn on/off the metronome.

Parameters:

• Action – Whether to toggle the metronome based on current state; turn metronome on, or turn it off.
• Sound – Whether to enable metronome sound
• Flash – Whether to enable screen flash

Adjust Metronome Volume

Modify the volume of the metronome.

Parameters:

• Action – if trigger is impulse, whether to assign a specific value, or nudge the value by some amount
• Value – if trigger is impulse, the value to assign/nudge
• Ramp – if trigger is impulse, duration over which to apply the change. A smooth ramp will be applied.
• Minimum Value – if trigger is continuous, the minimum value to assign, at the lower end of the  controller’s range
• Maximum Value – if trigger is continuous, the maximum value to assign, at the upper end of the  controller’s range
• Controller Input Start – if trigger is continuous, the incoming controller value to treat as the lower end of the range. Incoming values outside this range will be clipped to the given bounds.
• Controller Input End – if trigger is continuous, the incoming controller value to treat as the upper end of the range.

Toggle Ableton Link

Use this action to turn Ableton Link synchronization on or off.

Action: Toggle, Enable, Disable

Option: Set Tempo if Unset. When this option is on, turning Link on will set the project tempo to the current Ableton Link tempo.

Toggle MIDI Clock Sync

Turn MIDI Clock Sync on or off to the targeted devices.

Target: the midi source or destinations targeted by the action.

Action: Toggle, Enable, Disable

Undo

Undo the last action.

Redo

Redo the last undo step

Start New Project

Begin a new project.

Parameters:

• Confirm – whether to confirm first (if enabled, a second activation of the action will confirm).
• Save first – whether to save the current project before starting the new one.
• Template – if you have defined any project templates, the one to use for the new project.

Load Project

Load a project, with an optional cross-project transition.

Parameters:

• Confirm – whether to confirm first (if enabled, a second activation of the action will confirm).
• Save first – whether to save the current project before starting the new one.
• Quantization – how to synchronise the project load relative to the current timeline.
• Crossfade – The duration of crossfade from the current project to the new one.
• Effect Tails – Whether to blend audio from the current project with the new one, until effect tails (e.g. reverb or delay) go silent.
• Start Clock – Whether to start the clock of the new project running.
• Load Audio Units First – Whether to wait for audio units in the new project to load before beginning a transition.
• Copy Levels – Whether to copy the currently-assigned mixer levels from the current project to the new one.
• Project – The target project:
  • The next project in the same folder as the current project.
  • The next project in the current set list.
  • A specific project

Save Project

Save the project.

Parameters:

• Save As New – Save as a new project and leave the original project in its previous state

Adjust Master Volume

Modify the main output volume.

Parameters:

• Action – if trigger is impulse, whether to assign a specific value, or nudge the value by some amount
• Value – if trigger is impulse, the value to assign/nudge
• Ramp – if trigger is impulse, duration over which to apply the change. A smooth ramp will be applied.
• Minimum Value – if trigger is continuous, the minimum value to assign, at the lower end of the  controller’s range
• Maximum Value – if trigger is continuous, the maximum value to assign, at the upper end of the  controller’s range
• Controller Input Start – if trigger is continuous, the incoming controller value to treat as the lower end of the range. Incoming values outside this range will be clipped to the given bounds.
• Controller Input End – if trigger is continuous, the incoming controller value to treat as the upper end of the range.

Cancel Pending Actions

Cancel scheduled actions that have not yet been performed. Use this  action to cancel actions such as delayed actions that have been queued but not yet performed. In some cases (such as when there are series of actions that call other actions), you may need to call this action more than once to ensure that the actions are canceled.

Toggle Sequence

Turn Sequence mode on or off.

Parameters:

• Action – Toggle, Enable, Disable
• Remember Playback Position – whether to remember the sequencer playhead position when performing the action.

Toggle Mixer

Toggle, show or hide the mixer.

Toggle Session Recording (Coming in 2.0)

Toggle, Start or End a session recording using the current session recording settings.

Send MIDI Message

Send some MIDI to a MIDI target.

Parameters:

• Target – The target of the message: A connected MIDI device, an AUv3, another app running in the background, or a network MIDI destination.
• MonitorThrough – (For MIDI Color targets only.) When this option is turned on, MIDI sent to the color is sent through to the color’s destinations. When the option is off, the MIDI is sent to the color (typically for recording) but not passed on. When you are sending MIDI to a color for automation recording, you usually want to turn this option off to avoid feedback loops and double-triggering. This option is only available in Loopy Pro 2.0 and later.
• Takeover – (For MIDI Color targets only.) This option allows realtime manipulation of a widget to takeover from automation being sent from MIDI clips. For example, if you have a slider controlling a filter cutoff and the slider is being controlled by a MIDI Clip, you can takeover by moving the slider and the automation will take back over when the interaction goes idle.  This option is only available in Loopy Pro 2.0 and later.
• Message – The message to send: A PC, CC, Note, Pitch Bend or a Custom message (e.g. SysEx message). The Custom message is a series of MIDI bytes in hexadecimal format. In a custom message, XX can be use as a placeholder for the value of the widget (such as a dial, slider or knob) that is sending the message. When configuring, tap “Send” to immediately send the message, for testing purposes.

14-bit MIDI: From continuous widgets (such as faders and knobs), you can send the widget value as a 14-bit CC message. 14-bit MIDI messages are sent as a pair of MIDI CC’s with CC numbers that are 32 (20 hexadecimal) apart. For example, B005XXB025XX will send the widget’s value as a pair of CC messages that will be interpreted as a 14-bit value if the receiver knows how to handle 14-bit MIDI.

Select Controller Profile

Switch to, toggle, or enable/disable a particular control profile.

Parameters:

• Action – whether to enable a single profile from a list (radio style); toggle a control profile on/off, enable or disable a profile, or step forward or backward through profiles in a list.
• Target – the control profile to target, if applicable
• List – a set of control profiles to act upon, if applicable

Follow Actions are actions or action sequences performed after certain project and clip events occur. The Follow Action names are the names of events that trigger actions, not actions themselves. For example, in the Follow Actions panel Load Project doesn’t load a project. The actions that you add to the Load Project section are performed when a project first loads. Similarly, the Stop Clip follow action does not stop a clip. The actions in the Stop Clip section are performed when a clip stops.

Adding actions. Where Follow Actions are listed, tap on the +  to add actions for that trigger.

You might use follow actions to turn on an effect when a clips begins recording, and turn off the effect again upon record end. Or you might make one clip start another clip playing. You can even make chains of clips that start each other playing in turn, one after another.

You can define Follow Actions at the clip level (from a clip’s details panel), colour level (via the colour settings panel) or globally (project-wide) from the global Clip Settings panel.

The following events are defined for Follow Actions:

• Load Project
• Start Clock
• Stop Clock
• Begin Record
• Finish Record
• Begin Initial Record – see notes below
• Finish Initial Record – see notes below
• Begin Overdub
• Finish Overdub
• Play Clip – see notes below
• Stop Clip – see notes below
• Clear Clip
• Select Clip
• Deselect Clip
• Amplitude Envelope

Note that record, overdub and play follow actions are not mutually exclusive. A clip can be both playing and recording at the same time.

Play Clip and Stop Clip follow actions are triggered by the play/stop state of the clip changing whether or not the transport is running. Starting the transport does not trigger Play Clip follow actions of clips that are already play-enabled. When a loop is initially recorded, the play follow action is triggered when the recording ends and playback starts. If overdubbing happens while a clip is playing, it can be both playing and recording at the same time since overdubbing is also recording.

Begin Initial Record follow actions are triggered as soon as recording starts. Finish Initial Record, however, is called when the recording process has been finalized. Finalizing takes a small amount of time (usually a few milliseconds) after recording stops because a few things need to be calculated when the recording ends. As a result the Finish Initial Record follow action of a clip will happen after the Begin Initial Record  follow action of another clip whose recording stopped the first clip’s recording.

Because Finish Initial Record (and and sometimes Finish Record) may execute just slightly after recording ends, you do not want to use it if you need to guarantee that the actions it initiates are completed before the new clock cycle starts. Sometimes, you will want to use the Begin Initial Recording to trigger delayed/quantized actions that will happen when the clip will stop recording.

See also: for more follow action details, see this tech note on the Loop Pro wiki

Amplitude Envelope Follow Action

Loopy Pro provides a special Follow Action – Amplitude Envelope – which allows you to specify continuous value actions which map to the current clip volume as a clip plays.

You use this to implement sidechaining, where a parameter is controlled by an amplitude envelope. For example, you could configure an Amplitude Envelope on a colour representing your drum loops to drive the volume fader on a different colour for synth pads, for a sidechain compression effect.

Loopy Pro can be controlled via on-screen widgets, external MIDI controllers and typing keyboards (both USB and Bluetooth) via its flexible actions system.

Loopy Pro has built-in support for a number of popular controllers, including the Launchpad, the Akai APC40 mk2, and the MIDI Fighter Twister, and can be effortlessly set up to work with any other MIDI controller, via MIDI Learn.

Loopy Pro can be controlled by both MIDI Controllers and typing keyboards. The MIDI Learn system allows you to easily set up connections that we call bindings between controllers and Loopy Pro’s user interface, widgets and actions. Despite its name, MIDI Learn allows you to use typing keyboards (Bluetooth or USB) as well as any iOS-compatible MIDI device. There are two ways to configure how Loopy Pro responds to incoming controller events: via MIDI Learn itself or via Loopy Pro’s Control Settings screen.

MIDI Learn provides a simple, immediate way to attach an action to an on-screen element. Open MIDI Learn by either selecting “MIDI Learn” from the top-right menu, or by tapping the icon on the canvas editor.

In MIDI Learn mode, hotspots are shown with a shaded background: tap one of these elements to open the MIDI Learn panel for that item.

The panel displays settings relevant to the given action, and may provide a list of alternative actions by tapping the top-left “Actions” button.

While the MIDI Learn panel is active, Loopy Pro is listening for incoming MIDI messages from any connected device (tap  to connect any Bluetooth hardware you may have). Pressing a button or moving a knob on your MIDI controller will cause Loopy Pro to select that as the trigger for the shown action, thus creating a binding between the action and the incoming trigger.

Typing keyboard note. Loopy Pro currently only supports press/on when using typing keyboards for bindings. Off, press/release, release and the like are not possible with typing keyboard bindings.

Multi-Page Projects

Widgets. When a project has multiple pages, MIDI Learn for widgets has an option for determining to which page the binding applies: This Page Only or Active Page.

This Page Only means that the MIDI binding applies only to the particular item on this particular page. For example, if the first clip of the third page is the target, then the binding triggers the first clip of page three no matter what page is active. When the MIDI trigger comes in, the binding will trigger regardless of what page is active. This is useful for situations where you want to trigger an item even if its page is not visible.

Active Page means that the binding applies to the corresponding item of whatever page is visible when the binding is triggered. For example, if the binding is to the button on the page, it will apply to the first button of whatever page is visible at the time the binding is triggered. Note that if the order of objects differs on different pages, the target is determined by order/position not by the original target. For example, if Play All is the first button on page one and you learn that button for the active page, you are learning the first button on the active page. If Play All is the fifth button on page 2, the binding will trigger the first button not the Play All button. See this wiki page for more information about Active Page bindings.

Clips. When targeting clips in multi-page projects, the mechanism is a little different than for widgets. By default, the clip targeted is the particular clip on the current page. When the binding is triggered, that clip will be targeted regardless of what page is active/current. To target a binding so that it triggers the clip on the page active when triggered, you need to use the clip target browser. To bring up the browser, tap on the target field then tap on Specific Clip(s). The clip browser has a view for each individual page (with the page’s name displayed) and has a last view labelled All Pages. Selecting a clip on All Pages is the equivalent of using the active page for widgets. If you pick a clip on the All Pages view, the binding targets that clip on the current active page when the binding is received. Make sure that you de-select the clip on the particular page before swiping through to All Pages.

A trigger is an incoming MIDI message which can be bound to one or more actions. You can customise the trigger by tapping on the bottom trigger panel, shown with a shaded background.

Impulse Triggers

For impulse action types (as opposed to continuous actions that you might map to a dial), you can configure Loopy Pro to respond to:

• On state (e.g. a Note On, or value 127 CC),
• Off state (e.g. Note Off, on a zero CC),
• Either On or Off: Useful for MIDI controllers that only support toggle buttons, rather than momentary ones
• Hold – a hold is 500 ms between the on and off messages
• Double Tap – a double tap is two on messages arriving within 250 ms (with an intervening off message)

Hold and Double Tap

Hold and Double Tap MIDI triggers require that the controller be set up for fully momentary behavior: sending an ON message on press and an OFF message on release. Without both on and off messages, Loopy Pro is not able to detect hold and double tap. For note messages, ON is a velocity greater than 0 and OFF is velocity 0. For  CC messages, ON is a value greater than 0 and OFF is a value of 0. ON messages are typically a CC value or note velocity of 127. PC (program change messages) cannot be used for hold and/or double-tap.

Special Considerations. When Hold and/or Double Tap are set up as MIDI triggers in addition to On, there are a few things to understand. Normally, ON bindings are triggered as soon as the ON message comes in order to eliminate latency. No-latency triggering requires immediate processing as there is no way to know when that ON comes in to know when you plan to release the controller or if a second ON is coming. As a result, if double-tap or hold are mapped to the same message, they will trigger the On binding immediately and then the hold or double tap binding as appropriate unless you turn on the option to defer processing.

Avoiding double triggers. When setting up a Hold or Double Tap binding, there is an option available to Defer Other Actions. Turn this option on if you want to avoid triggering the ON binding when hold or double tap are also defined. This will result in a slight delay when the ON binding is triggered. For some action combinations, there are ways to have have immediate ON processing without double-triggers. See this wiki article for information about that.

Note: when triggering widgets by touch, Loopy Pro automatically defers processing of the press gesture when Long-Press or Double-Tap are also used to avoid false triggering the press. This means that there is always a slight delay.

Continuous Triggers

For continuous action types (such as a parameter adjustment), you can specify an incoming CC as Absolute or Relative; Loopy Pro may automatically detect this when you move the relevant controller knob. Absolute MIDI means that a controller sends values from 0 to 127 to represent the absolute position of the knob or fader. Relative MIDI means that a controller sends a message that indicates the direction the encoder knob is moving. For most continuous actions, you can also specify two ranges: A minimum and maximum value for the action (e.g. from -∞ dB to 0 dB), and a sub-range of the controller input. The former is used to limit the range of values of the parameter, while the latter can be used to allocate a sub-range of the available incoming values from the controller – to, for example, use the first half of a slider’s throw to adjust one parameter, and the second half of the throw to affect a different parameter.

Relative MIDI. Loopy Pro currently recognizes two relative MIDI conventions:

• 127/1:  Values from 127 down to 65 indicate the knob is moving left (decrementing) and values from 1 to 63 indicate that the knob is moving to the right (incrementing). Generally, you want to use 127 for left and 1 for right. A value of 127 is the finest decrement. The closer the value is to 65, the coarser the adjustment is. Likewise, 1 is the finest increment and the closer the value is to 63 the coarser the increment is.
• 64-centered (used by the MIDI Fighter Twister). In this mode a value of 63 indicates that the knob is moving to the left (decrementing) and 65 indicates that the knob is moving to the right (incrementing. 63 and 65 represent the finest decrement and increment. The farther the value is from these values, the coarser the adjustment will be.

 

 

A binding is a mapping between an incoming MIDI event or keyboard trigger and one or more actions that are performed when that trigger is received. Bindings are created when you MIDI Learn or manually create a binding in Control Settings.

Hotspots with bound actions in MIDI Learn are shown with a lighter shaded background. You can also view a complete list of bindings in the Control Settings screen, accessible from the main top-right menu in Loopy Pro.

See Control Settings for more details on editing bindings.

Loopy Pro control profiles store the MIDI and keyboard mappings we call bindings. Projects can contain one or more profiles. It can be useful to have multiple profiles for organizational purposes or  to be able to change the actions associated with MIDI bindings. For instance, your project might switch between “play mode” and “record mode” by changing the active profile.

Choose Control Settings from Loopy Pro’s main menu to access the profiles. Tap on a profile’s name to see the bindings it contains.

There are two kinds of profiles:

Project profiles allow you to store bindings that are saved within a project. You can reference specific project objects like clips and widgets, and references are persistent.

Global profiles exist outside of your projects, and are always available regardless of which project is loaded. You can have multiple global profiles and switch between them, either manually or via an action. Specific clips and widgets referenced from actions within a global profile are identified by their order on-screen, so rearranging your project canvas may result in the targets of some actions changing.

By default, for most connected MIDI controllers, Loopy Pro will send MIDI feedback for any currently-bound actions. For feedback, Loopy Pro sends the same MIDI message on the same MIDI channel used by the binding.

For example, if you have CC 20 on Channel 1 bound to a clip’s Play/Pause state, whenever that state changes Loopy Pro will send CC 20 on channel 1 back to the MIDI controller with a value corresponding to the current clip state. Similarly, if you have a CC set to control an AUv3 effect parameter whenever that parameter changes, Loopy Pro will send that CC back to the MIDI controller with the corresponding value.

This allows compatible hardware to display the current state of Loopy Pro.

If this is not desired, this can be disabled by opening up Control Settings, tapping the device name, and turning off the switch beside “Feedback Enabled”.

The MIDI feedback scheme used by Loopy Pro is the most common one used by controllers, but not all controllers respond to it. Some controllers don’t respond to MIDI feedback at all. Some controllers use a different feedback convention and expect feedback on a different MIDI Channel. Some controllers will echo back any MIDI they receive which results in a MIDI feedback loop.

Loopy Pro supports any controller capable of communicating via MIDI. However, there is enhanced support for certain controllers, to implement special features like RGB lighting.

This list is growing – see the Loopy Pro roadmap for details, or to request support for your hardware.

• Akai APC40 Mk2
• Akai APC Mini Mk2
• Akai APC Key 25 Mk2
• Launchpad Pro Mk2 and Mk3
• Launchpad X
• Launchpad Mini Mk3
• MIDI Fighter Twister

Loopy Pro’s Sequencer allows you to sequence each clip in your session, either by entering sequences by hand, or recording them using the sequence recorder. These sequences can be played back, or exported to a multi-track or stereo audio file.

You can  automate a live-looping session by sequencing your clips, and using the sequencer to trigger record and playback.

You can switch between sequencer/timeline playback and regular live looping with the Toggle Sequence action, and you can use MIDI Bindings and widgets to navigate the timeline with the Seek Timeline action.

Open the Sequencer by tapping the  button in the bottom-left navigation area.

Each row in the Sequencer represents an individual clip on the main canvas of Loopy Pro. You can reorder these rows by tapping and holding in the left area, and dragging up or down.

Zoom in or out by pinching in the main area to expand or contract the number of bars visible. Pinch to zoom vertically to grow or shrink each row. In version 1.x, vertical zooming needs to be done by pinching in the left column.

When a sequence exists, a new SEQ button appears on the top toolbar. Tap this to enable or disable the sequence.

Creating Sequences Manually

Create segments on the sequencer by tapping in the main area. Press and hold a segment from the middle then drag left or right to move it in the timeline. Drag from the end to expand the segment along the timeline, and drag from the start to contract it forwards. Tap a segment to select it, and to copy or delete it.

Segments will snap to the grid determined by the current zoom level. Zoom in – by pinching with two fingers in the main area – to zoom in and decrease the grid snap size. When zoomed all the way in, no snap-to-grid is applied.

Tap  in the bottom right of the screen to toggle selection mode; when active, you can tap and drag over segments to select them as a group.

Using the Sequence Recorder

You can also record sequences as you perform in Loopy Pro. Tap the  button on the top toolbar to open the Session Recording pop-up, then tap “Record Sequence”, to enable sequence recording.

Tap “Start Recording” to begin; Loopy Pro will count in for 4 beats, then begin recording. Any clips that are recorded, or played or muted, will be recorded to the sequencer timeline as segments.

Tap  again to stop recording.

You can use Loopy Pro’s sequencer to automate full performances, with recording actions and play/mute driven by the sequence.

When you have created a sequence, you can clear the audio out of sequenced clips – either via a swipe gesture on the clips on the main screen, or by double-tapping the waveform in the row header in the sequencer, and tapping “Clear” or “Clear All” – then an “Arm” option will be displayed in the row header.

Tap “Arm” to open the Arm Recording settings pop-up.

 

Turn on the switch beside “Arm Recording” to arm the clip. When the playhead reaches the first segment within the timeline, the clip will begin recording, for the length defined by the “Loop Length” slider.

If the segment is positioned at the very beginning of the timeline, additional options are presented, to determine how the session will begin.

• Count-In will cause Loopy Pro to perform a 1, 2 or 4 bar count-in with a metronome. This requires you to set the tempo in advance, and use in-ear monitors/etc to hear the metronome.
• Immediate Start will cause Loopy Pro to begin recording immediately, as soon as you initiate playback; if no tempo has been set in advance, stop recording by tapping the playback button (or bound controller), or by toggling recording on the clip by tapping it, or using a controller.
• Detect Loop will use Loopy Pro’s automatic loop detection to detect the loop, and automatically end recording on time. Set a tempo first (or set the detection range) to give Loopy Pro a hint about the loop tempo for increased accuracy. As soon as playback begins, Loopy Pro will begin recording, and automatically end recording on the beat when a loop is detected.

You can create looping regions on the sequencer timeline by tapping the  icon at the bottom right, or by tapping the timeline marker and tapping “Loop From Here”. Drag the start and ends of the loop marker in the timeline header to adjust the start and end, or drag from the middle to move the loop region backwards and forwards in time.

During playback, when the playhead enters the loop region, Loopy Pro will loop through the defined region continually, until you tap the play/pause button which shows the  symbol (or activate the controller bound to the Clock Pause action), whereupon playback will continue past the loop region when it is next reached.

You can use timeline looping in combination with sequence recording, to progressively record a sequence over several cycles. Timeline loops are also useful for marking a freeform part of a performance which may be of indeterminate length.

Tap the loop region in the timeline header to disable or delete the loop region, or tap   to toggle between enabled or disabled state.

You can export your sequence as a stereo mix with all effects rendered or as stems. To export from the sequencer, tap on the share icon that appears at the right side of the lower tool. If the mixer is visible, close it in order to make the lower toolbar visible.

The export options are:

• Stereo Mix – render a stereo mix with all effects.
• Multi-Track – export a separate audio file for each track of the sequence. Track effects and master bus effects are applied when rendering but not bus effects.

Clip Length

When clips are recorded in the sequencer, they receive a set length. A clip will also receive a set length if the clip is cleared while an event for it is in the sequencer even if the clip was not originally recorded in the sequencer.

Removing a pre-set length. If a clip has a fixed length as the result of being in the sequencer and you want to unset the length:

• Remove all sequencer events for the clip.
• On the loops page, open the clip’s details window and unset the length with the length slider.

Loopy Pro projects are flexible, customizable environments where you can combine and control multiple audio clips, effects, and inputs. They are central to how you organize your music and live performances. Projects are file bundles that contain the layout, audio and MIDI bindings. 

Loopy Pro creates new projects in the Loopy Pro folder on your device. You can move projects to other folders and accessible media using the iOS File browser. Loopy Pro can run and save projects that are outside the Loopy Pro folder, but you must open them from outside of Loopy Pro as its browser is restricted to what is found in the Loopy Pro folder.

Saving Projects

Because you often want to make temporary changes to a project, Loopy Pro does not auto-save the project. To make changes to your project permanent, you save the project. 

Loopy Pro features an auto-save-like function that allows you to leave and return to a project, preserving its exact state. While you’re working, the app continuously saves your progress within its Workspace project. When you create or open a new project, the Workspace is cleared. Before switching projects, Loopy Pro will prompt you to either save or discard your changes, ensuring your work is protected before the Workspace is reset.

Accessing the Project Manager

The folder icon in the upper-left toolbar provides access to the project manager and a list of recently opened projects.

Recent Projects List

Press and hold the folder icon to pop down a list of recently opened projects. You can also save your project or create a new one from the list.

Project Manager

Tap the folder icon to pop up the project save panel.

Features:

• New Project
• Save
• Duplicate Project: Create a copy of the current project as a new project. The original project remains unchanged and stays in the state it was last saved. This works similarly to “Save As.”
• Export: Export the current project or the project’s clips as audio.
• Pencil icon (Rename): Tap the project’s name to rename it. This action only changes the name and doesn’t create a copy of the project.
• Make Template Star: Activate the star at the upper-right to make the project a template or deactivate it to remove the project from the template list.
• Save Points: Tap to see and manage the project’s save points. See Save Points [link to section].
• Browse options: Projects, Recordings, Media.

The Browser

In the save panel, tap Projects, Recordings or Media to switch to the browser appropriate to the selected item. The browser lets you find, reorganize, and rename files and folders. Mostly, you see the same files and folders that you would see in the iOS Files app but there are some additional features.

Tap the Edit button to move or reorganize the files and folders.

Project Browser

There are a few items that do not correspond to items you can see in Files.

• Set Lists: Tap the Set Lists item to see, create and edit Set Lists.
• Recently Deleted: When you delete a project using the project browser, Loopy moves the projects here where they can be restored. Any project that remains for 30 days is deleted at that time.
• Audio Unit Extension Folder: Due to an iOS limitation, the Loopy Pro AUv3’s files are not visible in the Files app, and the AUv3 version cannot access projects from the standalone app. Instead, the AUv3 can only see projects stored in the Audio Unit Extension folder. Use the project browser to move files into this folder to make them visible to the Loopy Pro AUv3.

Recordings Browser

The recordings browser lists session recordings. Press the play button to preview the session recording or long-press to see and hear the session’s individual files.

Tapping the project manager’s Export button gives you the option to export the project or the project’s audio files. The standard iOS Share Sheet is presented for picking the destination. When exporting a project, save points are not exported. Use the iOS Files app to move or copy projects if you want to preserve the save points. Exporting audio files, exports the audio from all loops and one-shots. To export a mix from the sequencer, go to the Sequencer view and tap its share icon.

Exporting individual or selected clips

To export the audio from selected clips and one-shots, enter Loopy Pro’s layout edit mode, drag a selection rectangle around the desired clips, and then choose “Export” from the popup menu that appears.

To export the audio from an individual clip, show the clip details and tap on the Export (share) icon.

When “Use Save Points” is enabled in the System Settings panel, Loopy Pro automatically creates a recallable snapshot of your project as a Save Point. Restoring a Save Point brings the project back to the exact state it was in at the time of saving. Since Save Points include all project audio, they can increase the file size. Save Points are especially useful when making changes you might want to undo later. You can delete unnecessary Save Points as needed.

To access Save Points, open the project save panel and tap “Save Points.” This will bring up the Save Point browser, where you can restore or delete Save Points.

Templates are projects that serve as starting points for new projects. A project is made a template by tapping the project save panel’s star icon. When a new project is made from a template, a copy of the template is opened.

When there is only one template, new projects are automatically made with the template. If there is more than one template, you are presented with a list of available templates when you create a new project.

Using Loopy’s default template instead of your own. If you want to use Loopy Pro’s default project instead of your template, long-press New Project in the project browser. It will let you choose the built-in Default factory project template.

When a new project is started from a template, a copy of the original project is made and given a new name.

TIP! When saving a project to be used as a template, delete any unnecessary audio clips.

Use Set Lists to chain projects together in performance with seamless transitions. Switching projects is accomplished via the Load Project action. Use the action in an on-screen button, a MIDI binding, or a follow action  to chain projects together.

You create and manage Set Lists from the Project browser. In the project browser, tap on Projects tab then tap Set Lists towards the top of the project browser to access and create set lists.  Tap “Create Set List” to create a new set list; use “Add Project” to add projects to a set list. Drag the handles at the left to change the order.

Session recording has two different ways of capturing a performance: audio or sequence recording. Audio session recording captures the performance as audio files. A sequence recording captures the performance as events in the sequencer.

Audio session recording can capture everything that passes through Loopy Pro’s mixer including solos and other audio not contained in loops or one-shots. Sequencer recording creates a sequence of audio recorded or played into clips but doesn’t capture audio that you don’t record into clips.

Record Audio

To record and audio session, tap on the REC button and tap on Configuration to select what gets recorded. Tap Start Recording to start recording. Tap the REC button again to end the recording.

The session’s audio is captured to files in a uniquely named folder that ends “.lprecording”. Each session is recorded in its own folder. Loopy’s project window let’s you listen to a preview mix of session recordings. The actual files are accessible via Files app. They are found in the Loopy Pro folder.

Lossless Recording On/Off: By default, Loopy Pro saves session recordings as compressed (AAC/mp4) audio files. Turn Lossless Recording on to record uncompressed audio.

Capture options:

• Combined Inputs/Outputs – a stereo mix that captures all inputs and outputs to one file.
• Combined Outputs – the output to all external destinations as a stereo mix. If the mixer has output going to multiple channels, all the channels will be mixed together — included any destinations that share duplicate signals.
• Individual Outputs – the output of each mixer destination as a separate file
• Combined Inputs – each source’s input is captured to a combined stereo mix.
• Individual Inputs – each individual source input saved to its own file. Hardware input, audio units and IAA apps are all sources.
• Individual Color Groups – each color group’s output is saved to a separate file.
• Individual Buses – each bus channel’s output is saved to a separate file.

Audio from loops and one-shots recorded during the session is included in the relevant output file, but the individual clips are not saved as individual files. A project’s clips can be exported by separately if desired.

A session recording will often include several files. You can preview and browse session recordings and their files in the Project Manager’s recordings browser.

Record Sequence

Use this to capture clip-based performances. The performance is recorded as events on the sequencer timeline.

The Loopy Pro AUv3 can be loaded as an audio instrument, music effect (an audio effect that can receive MIDI input) or a MIDI processor. As an AUv3, Loopy Pro can be run as a multi-bus audio unit with multiple inputs (when run as an effect) and outputs. It can run as a MIDI processor for those times where you want to use Loopy Pro just as a MIDI controller.

Projects

The Loopy Pro AU project browser sees other Loopy Pro AU projects. Due to a quirk of how iOS handles AUv3 file storage, these files aren’t visible in normal file browsers. The standalone app’s project browser provides access to the AUv3’s projects. These appear in a folder called Audio Unit Extension folder (which is only visible to Loopy Pro). You can move projects into and out of the Audio Unit Extension folder using the Loopy Pro project browser.

Standalone and AU project compatibility

i(Pad)OS does not allow Audio Units to load other audio units. When moving standalone projects into the audio unit extension folder, you should remove any Audio Unit instruments and effects from the project.

State Saving Options

In the Loopy Pro AU, System Settings panel, there is a State Saving option. The Whole Project option will save all of the project’s data (including its audio) as part of the AU’s state. Project Reference Only saves only a reference to the project file found in the Audio Unit Extension folder. This option uses less memory and storage than the Whole Project option, but you must remember to save the project itself when you make changes that you want to keep.

Exposed AU Parameters

You can expose the elements of AU projects to the host as AUv3 parameters so that they can be manipulated with whatever tools the host provides for accessing AUv3 parameters. These will appear to the host as Parameter 1 through Parameter 128. To expose elements of your project as AU parameters, choose Exposed AU Parameters in the Control Settings panel.

The Loopy Pro AUv3 can be used as a multi-input/multi-output instrument or effect in hosts that support multi-in/out AUv3. Load it as an effect if you need to record external inputs. Load it as an instrument if you do not need to record from other sources.

By default, the Loopy Pro AU has one stereo input and one stereo output. For multi-in/out operation, add additional inputs and outputs to Loopy Pro’s mixer. To do this:

• Display the mixer by tapping on the mixer icon
• Tap on the + icon that appears next to the mixer
• Choose Add Audio Input or Add Auxiliary Output from the popup menu

Most of Loopy Pro’s configuration is done via the settings panels available from Loopy Pro’s main menu.

The Clip Settings panel has links to Playback settings, Recording Settings, Gestures and Follow Actions. These are global settings that apply to all of a project’s clips – these can then be overridden at the colour, clip, and action level.

Clips have a large number of recording and playback settings that can be used achieve a wide range of workflows. As mentioned in the Configuration overview, there is a settings hierarchy that allows colours and individual clips to have settings different from the project-wide settings.

For each setting, the project-wide setting is used unless it is overridden at the colour or clip level. Colours inherit their settings from the project-wide settings. Clips inherit the settings from their colour.

OVERRIDES

Colours and clips can override their inherited settings. An override setting becomes independent of the inherited setting. If you set a clip’s threshold recording setting, for example, it will be immune to later changes of that setting made at the project-wide or colour level.

Use the colour or clip settings panels to edit the overrides. When you look at a colour’s or a clip’s settings panel, any overrides that have been set up will be displayed. Tap the Edit Overrides button to edit the overrides for that section’s settings.

When you are editing overrides, a checkmark indicates that override is turned on for that setting. When an override is turned on, changes made at higher levels will not affect this setting.

Why does Loopy Pro show an override turned on even though it has the same setting as the inherited setting? Any time you turn on an override, it becomes independent of the inherited setting no matter what the setting is. You might turn on an override for the Threshold Recording setting, for instance, because you want to control that clip’s Threshold recording no matter what the global setting is.

REMOVING OVERRIDES

To remove an override, tap Edit Overrides, find the overrides setting and remove the checkmark next to the setting. Then, tap DONE.

As of Loopy Pro 2.0.6, overrides need to be removed manually in the settings panels. There is not an action to remove overrides though you may use the Assign Clip Settings action to change the setting used by an override.

The following settings define how clips play and stop. These can be overridden for particular colours and individual clips, as well as for individual playback actions.

COUNT-IN/OUT

 Play/Stop Quantization

Configure the synchronisation intervals at which loop play and stop events occur:

• None: Play and stop loops immediately, with no delay.
• Master: Play and stop loops in sync with the current clock master cycle.
• Loop: Play and stop loops in sync with the top (beginning/end) of the specific loop. The behavior of  Loop quantization is context-dependent. The overall goal is to start loops consistent with their length and to stop playback when the loop reaches its end. Exactly what that means depends on the context. If a loop is playing and is targeted to stop by itself, it will stop when it reaches its end. If a group of loops with loop stop quantization is targeted for stopping, playback of all of the loops stops when the longest playing loop in the group reaches its end. Shorter loops in the group may play through more than once. When a loop starts playing, it will sync with the longest currently-playing loop, if there is one — as  if Master quantization were on and the master cycle was the loop’s length – if not, it will start immediately.
• Custom: Define a custom sync interval.

Default value: Loop

One-Shot Quantization

Configure the synchronisation intervals at which one-shot playback begins. None: Play one-shots immediately. Master: Synchronise one shots with the clock master cycle. Custom: Define a custom sync interval. Default value: None

Second Quantization

When you activate an action a second time during a quantisation count-in or out, then if this setting is enabled Loopy Pro will begin a second-level 1-bar quantisation interval. If this setting is off, then the quantisation will just be cancelled, and the action performed immediately. During the second-level count-in, the action can be activated again to cancel this second count-in, and perform the action immediately. Default value: Off

ALIGNMENT

Phase Lock Loops

Keep loop playheads synced with the timeline/clock even when not playing. A phase-locked loop has a playhead that runs in sync with the master clock regardless of whether the loop is playing or not. Playing a phase-locked loop engages the playhead so that the audio is audible. Stopping a phase-locked loop disengages the playhead so that it is not heard even though the playhead keeps moving. If you want loops to start from the beginning when they start playing, turn off phase-lock. Non-phase-locked loops are called Free loops. Free loops only have a playhead while actively playing

If you turn off Phase Lock, then Play/Stop Quantization determines how loops will be synchronised with each other, as this dictates the start synchronisation. Default value: On

NOTE: Some actions (such as speed and rate changes) will turn phase-lock off. The Phase Align Clip action can be used to realign the clip with the master clock and turn phase-lock back on.

Time Fitting

Determine whether and how clips are fit to the project’s tempo.

• None – Clips won’t follow the project tempo at all. They will play at whatever their original tempo is.
• Time Stretch – Clips will be time-stretched to follow the tempo, keeping the pitch constant while adjusting the speed. When the tempo changes, Loopy Pro will perform a high-quality time-stretch operation in the background, while playing the clip using a live time-stretch operation. When the time-stretch processing is complete, Loopy Pro will switch the new audio over.
• Fast Time Stretch – As above, clips are time-stretched, but the live time-stretch operation (performed while Loopy Pro is processing the audio in the background) is less CPU-intensive, at the cost of fidelity.
• Varispeed – Clips will alter their playback rate to follow the tempo, with tape-style variable-pitch playback.
• Time-Fit One-Shots – Whether to perform time-stretching on one-shots while changing the tempo.
  • Never: Keep one-shots at original playback speed.
  •  Always: Always update one-shot speed to match tempo.
  • Auto: Decide based on length of one-shot – only one-shots longer than 4 beats will be time-stretched. This is the default.

Beat Quantization

Non-destructive playback quantization for MIDI and audio clips.

Beat Quantization can be applied to MIDI and/or audio clips, it is primarily intended for MIDI playback quantization. In general, we recommend using Beat Quantization for MIDI rather than recording quantization. Note: Audio beat quantization is an in-process experimental feature that will work better with some sources than others.

Beat/Grid Display
The display at the top of the Beat Quantization display shows the grid points to which notes are pulled when quantized. The lines are a sixteenth-note grid. The white dots are the grid points to which notes are quantized. The display is dynamically updated as the settings are changed.

The grid’s play button plays clicks at the grid points to sonify the quantization grid.

Quantization Types

• No Quantization
• Basic Quantization – Quantize to fixed grid points. Grid Spacing: Eighths, Sixteenths, 32nds, 1/8 Triplets, 1/16 Triplets, 1/32 Triplets. Options:
  • Intensity – How strongly to quantize the notes.
  • Swing – Swing places even numbered grid divisions later than they would normally be.
  • Randomness – Randomness moves notes forward and back by random amounts with the amount of possible shift controlled by its slider. Randomization is applied after all other transformations which allows you to humanize the even strongly quantized notes.
• Groove Quantization – Quantize to grid points derived from a MIDI or audio loop or audio file. Options: Intensity, Randomness
  • To delete a groove, swipe left on its name in the groove list.
  • To create a grove – Tap Create New Groove then choose the groove source:
    • Analyze Loop: Analyze an audio or midi clip in the current project for the groove.
    • Analyze File: Analyze an external audio file for the groove.

TRANSITIONS

Loop Boundary Crossfade

The amount of audio to blend across loop boundaries. When recording loops, Loopy Pro will begin recording a little early, and end recording a little late, and use this additional audio to blend smoothly across the loop boundary. Set this to longer values to create a very smooth, long fade (good for drones, for instance), or shorter values to create a shorter transition. Default value: 50ms

Fade In/Fade Out

The interval over which to fade in and out clip playback, rather than starting and stopping immediately. Set it to any duration, or:

• Microfade – No fade in/out, but Loopy Pro will perform a very short microfade to avoid clicks when starting and stopping. This is the default.
• Hard Zero – Disable even the microfade. You may hear clicks on start/stop if the clip does not already have appropriate audio boundaries. This is a reasonable setting if you don’t want to introduce additional smoothing on playback, which may interfere with initial transients.

MISCELLANEOUS

Hold to Play One-Shots

Whether to only play one-shots while holding. When this setting is on, releasing a one-shot will stop playback. Default value: On

Record If Empty

Whether to begin recording empty clips when triggered. If you disable this setting, tapping a clip or triggering it via an action/MIDI will have no effect. With this setting on, tapping an empty clip will begin recording. Default value: On

Pause Clock When Idle

If you stop all loops playing in a session, the clock will be paused until you start a loop playing again. Note that when a session is first opened, toggling a clip from stopped to play-enabled does not start the clock. Toggling a clip from being stopped to play-enabled unpauses the clock only if the clock has run at least once in the current session; this allows you to get clips into the desired Play/Stop state before starting initial playback. If you want play-enabling to always start the clock, use the Play/Stop clip action and turn on the the option Start Clock if Paused.

Default value: Off

 

The following settings define how clips record. These can be overridden for particular colours and individual clips, and can be customised for individual record actions.

RETROSPECTIVE RECORDING

Retrospective Recording

When this setting is on, Loopy Pro is continually recording into a buffer, set by the current clock master cycle length. When you trigger recording, this buffer is instantly copied to the triggered clip, allowing you to capture a loop after the fact. The audio that will be recorded depends on the Retrospective Quantization setting. Default value: Off

Retrospective Quantization

The quantisation interval to use when triggering Retrospective Recording. Immediate: Capture the immediately-preceding audio, regardless of position in the current cycle. Quantized: Capture the last cycle, aligned with the clock master cycle. If recording is triggered shortly before the start of a cycle boundary, Loopy Pro will capture the current cycle, continuing recording the live audio until the cycle is complete. Default value: Quantized

COUNT-IN/COUNT-OUT

Count In Quantization

The synchronisation interval for beginning loop recordings.

• None: Start recording loops immediately.
• Master: Wait until the beginning of the next clock master cycle to begin recording.
• Loop: If empty, use Master count-in. If the loop is not empty (i.e. when overdubbing), start recording in sync with the recorded loop.
• Custom: Define a custom sync interval. Default value: Master

Count Out Quantization

The synchronisation interval for ending loop recordings.

• None: Stop recording loops immediately.
• Master: Wait until the beginning of the next clock master cycle to stop recording.
• If empty, use Master count-out. If the loop is not empty (i.e. when overdubbing), end recording at the end of the existing loop.
• Custom: Define a custom sync interval. Default value: Master

Auto Count Out

When this setting is enabled, loops will record for the Count Out Quantization interval, and then stop recording automatically. This allows you to record loops of a pre-defined length without needing to manually end recording. If you disable this setting, clips will continue recording indefinitely, until you stop recording, and Loopy Pro will select an appropriate quantised length for the clip, if Length Quantization is enabled. See Pre-Set or Free Loops for further discussion. Default value: On

Overdub Count-In/Count-Out

Customize these settings to use different count-in/count-out settings for overdubbing and initial recording.

ALIGNMENT

Length Quantization

Whether to constrain loop lengths to multiples or subdivisions of a bar. Default value: On

Pad Loop Length

When recording a new loop and ending record before the set quantisation interval, whether to extend the loop with silence to the full interval. Default value: Off.

Phase Preservation

Whether to rotate new loops so that the start point is aligned with the current musical phase. The musical phase is determined by the longest playing loop.

If you disable this setting, Loopy Pro will perform no adjustment, so the start of the loop will be the point at which you began recording, which may not be what you expect. Default value: On

Example: Say you have a 2-bar drum loop and 12-bar rhythm guitar and bass tracks playing. If you start recording a new clip 4 bars into the cycle and record for a full cycle, your new clip will be rotated so that when you play it from the beginning where you started recording will be 4 bars into the clip which lines up with the other clips. If phase preservation were turned off, your clip would start where you started recording and would not line up with the loops that were playing when you recorded.

THRESHOLD RECORDING

Loop Threshold Recording

When on, audio loops will wait for the input level to cross the defined audio threshold before recording starts. For MIDI loops, recording starts when the first MIDI note message arrives.

You can use this facility to “arm” a loop in advance, which will only start recording when you begin playing. Default value: Off

One-Shot Audio Threshold Recording

When on, one-shots will wait for the input level to cross the defined audio threshold before recording starts. For MIDI one-shots, any note on message triggers the threshold. Default value: On 

Audio Threshold

The level meter labeled Audio Threshold sets the audio level that triggers recording when threshold recording is turned on. This applies to audio loops and one-shots. This is a global setting that applies to all audio threshold recording.

INTRO AND TAIL

Record Intro

When enabled, Loopy Pro will begin listening immediately upon starting a record count-in. If the audio level crosses the threshold, recording will begin immediately, and the audio will be recorded to a special “intro” section of the loop, which will play back when starting the loop playing. This setting requires Count In Quantization to be enabled. See Intro and Tail for further discussion. Default value: Off

Record Tail

When enabled, Loopy Pro will continue recording for a short time after loop recording ends. Recording will continue until Loopy Pro detects that the audio level has dropped off. The audio will be recorded to a special “tail” section of the loop, which will play back in the second and latter repeats of a loop, and when the loop is stopped. See Intro and Tail for further discussion. Default value: Off

MIDI

MIDI Recording Quantization

MIDI recording quantization is destructive quantization applied to recorded MIDI. The options are the same as for beat (playback) quantization. It is often preferable to use playback rather than recording quantization

MIDI Control Overdubbing

This setting determines how non-note MIDI data is treated when overdubbing. This helps avoid conflicts between existing automation events and new ones.

• Keep Existing Events – New events are added and old ones left untouched.
• Replace While Adjusting (Touch) – Replace old events for a given parameter (a particular CC, for instance) while the parameter is actively being adjusted. Stop erasing old events shortly after movement ceases.
• Replace (Latch) Until Loop End – Once movement starts, past control events are removed until the loop’s end boundary is reached, resetting with each loop cycle.
• Replace (Latch) Until Record End – Once movement starts, past control events are erased until the end of the overdub session.
• Full Overwrite – All previously recorded control events are overwritten during overdubbing.

MISCELLANEOUS

Simultaneous Recording

When enabled, you can record multiple loops at the same time. If disabled, when you start additional loops recording while a loop is already being recorded, the additional loops will enter a record queue, and each loop will be recorded one after another. Default value: Off

After Recording

Configure how a loop behaves after its initial recording has completed. Play: Loop will begin playback immediately after recording. Stop: Loop will be silent after recording. Overdub: Initially begin overdubbing, for recording additional layers. Default value: Play

Wait for Playback

With this setting enabled, when the clock is paused and you start a loop recording, Loopy Pro will not begin recording until you unpause the clock. If this setting is disabled, Loopy Pro will automatically unpause the clock and begin playing when you start recording. Default value: Off

Auto Loop Detection

When enabled, Loopy Pro will automatically detect and trim the first loop of a session, allowing you to create tight, well-timed loops without having to be precise with the record start and end timing. See Automatic Loop Detection for more discussion. Default value: Off

Auto-End Detected Loop

With this setting enabled, Loopy Pro can automatically detect a loop of the given length, end recording and begin playback, allowing you to record the first loop of a session entirely hands-free. You must first set either the master cycle length or a clip’s pre-set length, and it’s recommended that you also set a rough tempo to assist accurate detection. Default value: Off

 

Configure the on-screen gestures for interacting with clips here. You can assign your own actions for Tap, Two-Finger Tap, Swipe, Swipe Up, Swipe Down, Swipe Left, Swipe Right and Long Swipe. These gestures can be overridden at the colour and clip levels.

See: Gestures

Set up Follow Actions here, in conjunction with Loopy Pro’s powerful actions system to perform actions when certain events occur, like clip playback, recording, or upon project load.

The Color Groups screen allows you to add, remove, and configure colours in Loopy Pro.

Here, you can provide a name for colours – which appear as tracks in the Mixer, as well as elsewhere – and set the volume, balance, pitch and playback speed of clips within each colour.

You can specify custom playback and recording settings per colour.

This area of Loopy Pro is where you can customise the behaviour of your controllers, as an alternative to MIDI Learn.

OSC

Here, you can enable Loopy Pro’s OSC server, allowing you to control Loopy Pro from other OSC-compatible software and devices.

Use the OSC Actions Directory to look up OSC addresses for actions, and enable feedback for individual addresses (requires a TCP OSC connection).

When using OSC, you can use the provided OSC addresses as listed in the directory, or you can use your own addresses and make bindings within Loopy Pro using the (uh, increasingly inaccurately-named) MIDI Learn feature.

Enable Network MIDI

If you wish to connect to Loopy Pro via MIDI over network, enable this here. This is disabled by default in Loopy Pro 1.1 and onwards due to an ongoing iOS MIDI bug, where network MIDI interferes with MIDI connections.

MIDI Devices

All MIDI devices connected to Loopy Pro appear in this section. Tap to configure the device.

• Device Type – Tell Loopy Pro if you want this device to be treated as one of the supported controllers, like the MIDI Fighter Twister. Note that Loopy Pro will automatically identify many supported devices, like the Akai APC40 mk2 and the Launchpad, via a MIDI Universal Device Inquiry exchange. Only those supported controllers that do not respond to MIDI Universal Device Inquiry will be shown here.
• Feedback Enabled – Whether to send feedback for bound actions to this device, such as playback state, or parameter values. This is on by default; if your device behaves unexpectedly, this can be disabled.
• Use MIDI Timestamps – By default, Loopy Pro will perform actions at the time a MIDI message is received. This generally gives the best response, but if you are experiencing timing issues, you can enable this setting to force Loopy Pro to use the MIDI timestamps provided by the device instead.

Current Project

Edit the control profiles for your currently-loaded project here.

Project profilesallow you to store bindings that are saved within a project. You can reference specific project objects like clips and widgets, and references are persistent.

You can also edit the global Follow Actions here.

See Editing Bindings below for further discussion.

Global Profiles

Edit global profiles here.

Global profiles exist outside of your projects, and are always available regardless of which project is loaded. You can have multiple global profiles and switch between them, either manually or via an action. Specific clips and widgets referenced from actions within a global profile are identified by their order on-screen, so rearranging your project canvas may result in the targets of some actions changing.

See Editing Bindings below for further discussion.

Editing Bindings

There are two primary ways to edit bindings in Loopy Pro: Here, in Control Settings, or via MIDI Learn.

MIDI Learn provides a fast, simple interface, allowing single actions to be bound quickly.

In Control Settings, you have more control over creating custom bindings, with the ability to chain multiple actions together in custom sequences, with support for doing something different with successive button presses, or performing a timed sequence of actions, or combinations of both.

Tap a control profile, either in Current Project or Global Profiles, to open the profile editor. Here, the bindings that are saved to the profile are shown, along with controls to rename the profile, duplicate it, or export it.

Tap “Add New Binding” to create a new binding. You will be presented with a directory of possible actions to perform. Select one, and configure it, then tap “Save” to store the action to your new binding. Loopy Pro will then listen for incoming MIDI/OSC messages – when it receives one, it will bind the action to this message. You can also manually select the trigger by tapping in the “Trigger” field.

You can add multiple actions by tapping “Add Action” – for example, you can have a dial adjust multiple parameters simultaneously, perhaps changing different parameters at different sections of the control’s value range. Or, you can have a button push perform multiple different things, such as enabling an audio source before beginning a loop recording.

The Synchronization menu gives you access to all the settings for synchronizing Loopy Pro with other applications and devices. Loopy Pro can use both Ableton Link and MIDI Clock and can be used to bridge Ableton Link and apps or hardware that use MIDI Clock.

Ableton Link

Options:

• Sync Start/Stop: Start and Stop with the Ableton Link clock
• Act As Master: This option is a custom Loopy Pro option used when you need Loopy Pro to behave like a master device when using Ableton Link. When this option is on, Loopy Pro ignores other apps’ tempo changes and starts playback immediately without waiting for the Ableton Link clock to begin a new cycle.

Understanding Ableton Link

Ableton Link is designed for cooperative behavior unlike MIDI Clock. With normal Ableton Link behavior, no app or device is the master. It operates entirely cooperatively. Link maintains the clock not an individual client. Any client can change the tempo or start/stop the clock. Link shares precise tempo information, beat information and bar boundaries.

With Link, any client can change the tempo and the other clients change also. Normally, when a client starts, it starts at the beginning of Link’s next clock cycle. This makes it easy for all clients to start and stop on bar boundaries. When you press play, there is usually a short wait until Link reaches the next bar boundary.

Key MIDI Clock Differences

With MIDI Clock, one app or device is the clock master. All the clients follow the clock sent by the master. MIDI Clock does not have precise tempo or bar boundaries. It is just a a series of pulses. Each clock client calculates the tempo from the received pulses. There is no notion of bar boundaries, so you need to take care to start your apps and hardware at the beginning of a measure to keep their measures aligned.

Act As Master

Loopy Pro’s Act as Master option allows Loopy Pro to act somewhat like a MIDI clock master for situations where you want Loopy Pro to start immediately and need Loopy Pro to always control the tempo. When this mode is on, any link clients set to start/stop automatically are likely to start one measure after Loopy does since they need wait for the beginning of the Ableton Link clock’s next cycle.

When this option is on, Loopy Pro is not behaving like a normal Ableton Link client and may have surprising impact if you aren’t aware of how Ableton Link normally works.

MIDI Clock Settings

Loopy Pro can send and receive MIDI Clock. When sending MIDI Clock, it also sends MIDI SPP (Song Position Pointer) messages so that clock clients can keep their songs and sequences aligned with Loopy Pro’s timeline.

Start vs. Continue

Loopy Pro sends MIDI Clock Start messages when you press the transport play button. If you are recording a first loop that sets the tempo, Loopy Pro sends a MIDI Clock Continue message and a MIDI Song Position Pointer message that indicates the length of the first loop.

MIDI Clock Sources

If you want Loopy Pro to follow another app or device’s MIDI Clock, choose it from this list. Be aware that when an audio application like Loopy Pro follows MIDI Clock, it must constantly adjust the audio (time-stretching) to keep it synchronized. This can impact audio quality and increases CPU usage. Generally, you want Loopy Pro to be the MIDI Clock source rather than a client.

Options:

• Offset: Use the Offset slider to achieve tighter sync.
• Sync Start/Stop: Turn this option to have Loopy’s transport started and stopped by MIDI Clock Start, Stop and Continue messages

MIDI Clock Destinations

Select any apps or devices here to which you want Loopy Pro to send MIDI Clock. An offset slider, let’s you offset the clock to achieve the tightest possible synchronization.

The Clock Settings panel gives you access to useful options related to Loopy Pro’s clock and transport. This panel is also displayed when you press the clock panel’s gear wheel icon. See The Clock for details.

Choose System Settings from the main menu to access the System Settings panel.

Play In Background

When this option is on, Loopy Pro is fully-operation when it is in the background. When it is off, Loopy Pro stops processing audio when it is not the foreground app. When Play in Background is off, Loopy Pro needs to re-activate plugins when it comes back to the foreground which can take time.

Orientation Lock

When orientation lock is on, rotating your iPad or iPhone will not change the orientation of the current layout in this sense: whatever is in the upper-left will remain in the upper-left after rotation; whatever was in the lower-right will remain in the lower right.

Sample Rate

Choose from available sample rates. Generally, changing the sample rate changes the sample rate of the attached audio interface if there is one. Some interfaces do not respond to host requests to set the sample rate.

Buffer Duration

This setting sets the OS’s audio buffer length. The audio system has a buffer that collects audio to be processed. The larger the buffer is, the greater the latency. The smaller the buffer is, the higher the computational demand. Small buffers can make it hard for the device to keep up with the processing demand which can lead to audio crackling.

File Format

The choices are uncompressed 16, 24 or 32-bit files or AAC compressed files.

Use Save Points

Turn this option on to use Save Points which are recallable project snapshots created when you choose Save Project. See Save Points.

Auto_Mute Audio Sources

When this option is on, disconnecting your audio interface automatically mutes audio sources that might cause feedback.

Enable Network MIDI

When this is on, a Network MIDI Session is made active. This option is off by default as we have found that when Network MIDI is on, it can reduce stability and can interfere with MIDI operation. When you turn it on, Loopy Pro will ask you to re-consider.

Multiroute Audio

Multiroute Audio is an OS feature originally intended to allow you to use the wired headphones  while also using an audio interface for output. Its behavior is somewhat unpredictable and out of the audio host’s control. Bluetooth audio devices and AirPlay are not supported in this mode.

Some people report that they can send output to multiple attached audio devices when Multiroute is on, but we have found it somewhat unpredictable and generally recommend that it be left off.

We have sometimes found that turning it on and then off can fix audio connectivity problems.

Accessibility – Show Color Labels On Clips

When this option is on, Loopy Pro will show text indicating the color of the project’s clips.

Loopy Pro uses your preferred language for its menus and text. It defaults to the language used by your device. If you prefer to use English, you can change that in the Loopy Pro settings in the iOS Settings app:

• Make sure that English is turned on as a language option on your device by going to the iOS Settings app and looking in the Language & Region settings.
• In the iOS Settings app, find the Loopy Pro settings page.
• Set the language preference to English.

Loopy Pro stores your non-AU projects, global profiles and effects preset settings in the Loopy Pro folder found in the Files app On My iPad or On My iPhone. Make a copy of that folder to your preferred location to back up your non-Audio Unit Loopy Pro data.

If you use Loopy Pro as an audio unit, the saved projects are in a pseudo-folder that you see as Audio Unit Extension Folder in Loopy Pro’s project browser. Unfortunately, due to a quirk of iOS, that folder is not actually in the Loopy Pro folder or visible in the Files app. To back up your audio unit projects, use one of the following methods:

• Method 1: Open each AU project in the Audio Unit extension folder. Use Export from the project browser to export the project to your preferred back up location.
• Method 2: In Loopy Pro’s project browser, make a folder into which you will temporarily move your audio unit projects. Use the project browser to move the contents of the Audio Unit Extension folder to the backup folder you just made. In Files app, copy the backup folder to your preferred backup location. Back in Loopy Pro,   use the project browser to m0ve the contents of the backup folder back into the Audio Unit Extension folder.

The desktop backup program iMazing is a useful tool for backing up iPads and iPhones as it allows incremental retrieval of backed up application data unlike iOS’ native backup/restore procedure that requires a full restore of the entire device.

Need some more help?

The Loopy Pro Wiki is a growing source of information about Loopy Pro.

Loopy Pro has a number of active communities full of experienced users that are happy to help. The communities are a good source of information and insight into how people use Loopy Pro and what equipment they use it with.

Join Loopy Pro Community

Prefer to talk to us directly? You can also email us at [email protected]

Why can’t I use my AirPods/other Bluetooth audio gear?

This is a quirk of Measurement Mode, a feature that Loopy Pro’s echo cancellation requires. If you turn off echo cancellation, Loopy Pro will also turn off Measurement Mode, allowing access to your Bluetooth hardware. Open the mixer, tap the microphone icon at the top of the hardware input channel strip, then turn off the switch beside “Echo Cancellation”.

Why does the speaker go quiet when I start screen recording?

Another Measurement Mode quirk, I’m afraid. See immediately above for instructions to disable echo cancellation. Note: you will lose the benefits of echo cancellation, so it’s important that if you plan to record from the mic that you use headphones, or external audio gear.

Can I edit MIDI automation in the piano roll?

Currently, only note data can be edited in the piano roll editor. We will be adding automation editing in the future.

Can Loopy Pro record MPE in MIDI clips?

Yes, it can

Where can I find answers to other questions I have?

The Loopy Pro Wiki is a good source for information and includes answers to many other frequently asked questions.

If you are having trouble, see the Troubleshooting page of the Loopy Pro wiki.

If Loopy Pro or another third-party app is crashing, and dumping you back to the home screen, it can be very helpful to see the associated crash log so that I or the developer of the third-party app can fix the issue. While we may get anonymised versions of these in a big lump, it can be difficult to tie certain events to individual crashes, which can sometimes be  necessary for nailing a bug.

If you’re up for it, finding and sending me a crash log can go a long way towards solving the crash. Here’s how to find and send them in:

1. Open the Settings app
2. Find Privacy & Security; tap it
3. Find Analytics & Improvements; tap it
4. Find Analytics Data; tap it
5. Look for entries with the app name (i.e. Loopy Pro, or Loopy Pro AU, if it’s Loopy Pro or its AUv3 that crashed), with the date/time that matches when you saw the crash. Note that any entries with “wakeups” in the name aren’t actually crashes, but another kind of log that isn’t much use for diagnosis: Ignore those ones.
6. Select the entry, then tap the share button at the top right (a square with an upwards arrow) and email the contents to [email protected].

Crashes on Load

If Loopy Pro actually crashed on load, Loopy will move the current workspace away and then open a blank project. It may help diagnose the issue if you send me the crashed workspace: you can find this by opening up the Files app on your device, the navigating to “On My iPad” (or “On My iPhone”), then finding “Loopy Pro”. Long-press on the “Workspace (Crashed)” file within the Loopy Pro folder (or “Workspace”, if it hasn’t been moved away yet), then tap “Compress” to make it into a zip file. Then long-press on the newly-created zip file, tap “Share”, and email it to me at [email protected]. Thank you!

In some cases, it can be helpful to see some more diagnostics from your device, and I may ask you to send a sysdiagnose. Sysdiagnose is a built-in iOS utility which records a variety of diagnostic information to a file that can be sent to Apple or to developers.

To provide a sysdiagnose:

1. Write down, as precisely as possible, the time that the issue we’re diagnosing occurred. That’ll help me find it in the (huge) log file.
2. Simultaneously press and release both volume buttons + sleep/wake (power) button. The sysdiagnose is triggered upon button release; you won’t see or hear anything (iPhone will vibrate), but it’ll be running in the background.
3. Wait a few minutes for the diagnostic gathering to complete.
4. Open Settings, and find Privacy, Analytics, Analytics Data, then search for the sysdiagnose entry in the list. It’ll start with “sysdiagnose”; the list is alphabetically sorted, so scroll down a bit.
5. Tap the entry, then tap the share button at the top, and email the file to me. The file is quite large so I recommend doing this on WiFi. If the email setup won’t send the file, we might need to work out an alternative, like using Dropbox instead.

Version 2.0.5

• Added new “Play Group Mode” action
• Added “Join” function for multi-project session recordings, to combine related tracks across projects for easier import into a DAW
• Added option to bypass “Use Link Tempo” prompt on load
• Added Assign Group Settings convenience action
• Fixed issue where changing MIDI destinations could cut off unrelated playing MIDI
• Re-added support for solo actions affecting one shots
• Added default visibility icon to add effect screen
• Revised appearance of on-off effect state button in add effect screen
• Fixed a couple of crashes

Version 2.0.4

• Fixed an issue where the “Count-In Only” metronome setting wasn’t working properly when clock count-in was enabled
• Added “Original Tempo” option for all imported clips, even if time-stretching is turned off
• Fixed a crash when exporting from the sequencer
• Fixed colour selection indicators not showing correctly sometimes
• Fixed an issue with IO buffer duration not being set correctly on startup sometimes
• Fixed issues with some input hardware with many channels
• Fixed scene buttons not following the cursor on APC Mini Mk2 and Key 25 controllers
• “Mute/Unmute Audio Source” action now respects the Mute Position default from the mixer configuration

Version 2.0.3

• Ignore “Wait For Playback” when Audio Threshold Recording enabled
• Fixed issues with OSC bindings
• Fixed “Monitor Through Color” icon missing colour if empty of clips
• Fixed some crashes

Version 2.0.2

• Fixed a hang when using quantized retro recording

Version 2.0.1

• Support for mono-only Audio Units
• Improved clip recording performance
• Fixed rare hang during layout on some projects
• Fixed memory leak in AUv3 plugin
• Resolved issue with retro overdub feedback
• Fixed visual alignment glitch when recording MIDI clips
• Fixed crash when rotary encoder is mapped to clip speed
• Fixed issues with Send MIDI action when targeting MIDI colors
• Purchasing upgrade now works correctly when a free license is active
• Various crash fixes and stability improvements

Version 2.0

Major Features

• MIDI Clips
  Integrate MIDI into your loops and one-shots seamlessly. Record, edit, and playback MIDI like never before.
• MIDI Sequencer
  Compose and edit MIDI clips with precision using the new sequencer for detailed control over every note.
• Polyphonic Clip Playback
  Play loops or one-shots in polyphonic pitch or slices (divided by transients or evenly), from a MIDI controller or a MIDI clip.
• Automation via MIDI
  Use MIDI clips to record and play back automations to control any aspect of your project.
• Bus-to-Bus Routing
  Route audio between buses for flexible mixing setups by adding sends to buses within your session.
• Beat Quantization
  Quantize transients for MIDI and audio clips (“warp”) to create grooves with swing, randomization, or custom feel.
• Revised Mixer, with Collapsible Mixer Groups and Sources Row
  Streamline your workspace by collapsing mixer sections selectively for easier navigation, and see the whole signal chain for each channel with the new “Source” row.
• Dockable Panels
  Dock plugin windows to any screen edge for a customised workflow.

Other Features

• On-Screen Keyboard
  Add an on-screen MIDI keyboard as a MIDI source for quick and easy note entry.
• Rotary Encoder Widgets
  A new encoder widget for adjusting continuous relative values.
• Improved Canvas Editor
  Select and scale multiple elements at once.
• Assign Clip Settings Action
  Adjust clip settings dynamically at the clip, color, or global level through actions, for staggeringly flexible project setups.
• Clip Offset Action
  Shift your clip offset on-the-fly with a new action. Works great with the new rotary encoders.
• “Next Empty Clip” Action Targets
  Target the next empty clip for an action, in your whole project or in a particular color or play group.
• Stepped Dial/Radio Trigger Controls
  Configure Stepped Dial and Radio widgets with options for action triggering on change, release, or “Retrigger” action, allowing deep stateful actions programming.
• Overdub Auto Count-Out
  Auto Count-Out for overdub recordings—set it up to streamline your recording sessions.
• Append One Clip to Another
  Concatenate clips with the “Merge” action.
• New Hardware Support
  Full built-in support for the AKAI APC Mini mk2, and the APC Key 25 mk2.
• New Languages
  Translated into: Chinese (Simplified and Traditional), English, French, German, Indonesian, Italian, Japanese, Korean, Polish, Portuguese (Brazilian), Russian, Spanish, Thai, Turkish, and Vietnamese
• So much more
  • Individual cycles setting for peel/replace to add and remove multiple overdub layers with a single action or step through each layer individually.
  • Cross-project session recording, and a new action to toggle session recording via a controller or widget.
  • Latency compensation for MIDI controllers.
  • New “Select” and “Deselect” clip follow actions.
  • Plugin preset import and export.
  • New “Use Direct MIDI Value” setting for stepped dial/radio widgets’ MIDI control.
  • New playback and recording settings interface for clips and colors, showing specific overrides only.
  • Increased to 128 save slots for parameter save and restore.
  • Copy and paste multiple actions at once by long-pressing in the header above a list of actions.
  • New “Correct Clock Tempo” action.

Fixes & Improvements

• Improved Controls
  Fine-tuned control speed settings, slider adjustments, and improved interaction with the sequencer.
• Session & Project Stability
  Addressed several stability and performance issues, including session recording reliability, session playback, and undo handling.
• Performance Enhancements
  Many important performance improvements for a snappier interface, faster project loading, and reduced power consumption.
• New & Updated Libraries
  Updated the Rubber Band time-stretching library to the latest version for cleaner, significantly higher-quality tempo and pitch control.
• Quality-of-Life Updates
  Solo on recording clips, improved synchronization features, improved sequencer interactions, improved stepped dial and radio grid widget control, assorted visual improvements, smoother transitions in and out of time stretching, and lots more.

Version 1.1.24

• Added “Show Hold Button” option for X/Y Pads (default: on)
• Switch to main screen when prompting for clips, if elsewhere
• When unmuting hardware audio source at input, remove auto-mute as well
• Increased maximum displayed stepped dial/radio actions from 32 to 128
• Made waveform display follow track duration when multiplying/dividing/etc

Version 1.1.23

• Fixed issue with binding impulse actions, where hold/on-off actions were bound instead of impulse ones
• Fixed an issue that could cause an AUv3 crash
• Fixed a crash in preset action configuration
• Fixed “Simultaneous Recording” override at clip level

Version 1.1.22

• Fixed issue where merge action could occur before a record was finalised
• Fixed issue that could break relational clip subjects (“Next Clip” etc)
• Fixed crash when selecting effect target for preset and open interface actions

Version 1.1.21

• Fixed an issue with value ramping for “Trigger Widget” actions

Version 1.1.20

• Added new Save/Restore parameter actions, to store values of selected parameters, and recall them later. Even works across multiple plugins. Preset morphing!
• Added new “Toggle Sequence” action: Turn the sequence on or off, with the option to resume at prior playback position. Great for pausing a sequenced session for a jam, then jumping back into the sequence after.
• Added “Individual Outputs” option for session recording: Record your output channels separately.
• Added continuous adjustment of clock phase, via Phase Align Clock action: Move the downbeat around, relative to your playing loops.
• Added thumbnail icons for projects
• Added support for 3FH/41H (midpoint 64) relative CC encoding (used by MIDI Fighter Twister, for example)
• Added work-around for an iOS bug that reports incorrect number of audio interface input/output channels
• Added new Stop vs Retrigger settings for “Already-Playing One-Shots”
• Fixed an issue with load project action not starting
• Fixed some gesture conflicts that could result in delayed record end if a double-tap or hold present
• Fixed issue with Track Phase Align when transitioning from reverse

Version 1.1.19

• Added a new sample template: Adam Searan’s Simple 4 Track Looper
• Added “Phase Align Clock” action
• Added support for second parameter for OSC state feedback messages, containing current unscaled parameter value
• Added “If Counting In/Out” setting for record actions
• Added “Set Tempo If Unset” option for Link toggle action (on by default)
• Implemented new frictionless trial system
• Fixed a crash when sending long SysEx messages with the Send MIDI action
• Fixed a sporadic phase align action issue when clip playing in reverse
• Fixed an issue with automatic audio source muting
• Fixed issue with making multiple parameter bindings using plugin parameter discovery button
• Fixed state feedback issue with stepped dial/radio widgets with “Deselect” actions present

Version 1.1.18

• Added configurable return-on-pause for play/pause button (find in Clock Settings, or long-press play button)
• Added dedicated rewind button on sequencer toolbar
• Added “Toggle Mixer” action
• Added MIDI channel remapping option for MIDI destinations
• Added warnings for some problematic conditions: low disk space, Network MIDI or Multiroute Audio enabled
• Avoid redundant saves when terminating/moving to background
• Allow Stepped Dial widgets to track state of their individual actions
• Allow “mutually exclusive” groups with “independent” types
• Improved canvas element copy/paste
• Implemented rendering of overdub decay in clip waveforms
• Tweaked ‘clips play independently’ play group behaviour when playing/recording a member while others counting-out
• Tweaked behaviour of retro recording to allow completion of record even if buffer not yet filled enough
• Added a workaround for a MIDI system bug that prevented saving profiles for some problematic hardware (looking at you, Tascam Model 12!)
• Fixed some issues with adding audio sources in certain conditions
• Fixed a gesture conflict between hold-to-play one shots and a record action on tap
• Fixed a possible hang when importing mp3 files
• Fixed audio source mute action when ramp specified
• Fixed AUv3 keyboard focus workaround issue which might cause flickering
• Fixed clip slicer hold to play
• Fixed issue where active clip might not continue playing after tempo set following clock reset
• Fixed issue where playhead jumps after disabling a timeline loop region while looping
• Fixed issue with some volume/gain actions when toggling between values
• Fixed issues with tempo x/÷ correction, and time scaling after tempo reset, where ‘original tempo’ could be set to incorrect values
• Fixed swipe on one shots with certain configurations
• Tweaked audio source automatic muting to avoid possible incorrect unmute on load
• Fixed missing waveform layer rendering in sequencer
• Fixed Musical Typing treating enter key as sustain (should be just tab)
• Fixed issues with chaining record of clips with overdub-after-recording set (Simultaneous Recording off)
• Fixed “Waiting for Clock Start” state when starting second loop recording while first loop still recording (it should just begin recording)
• Avoid unexpected record start of record-on-touch clip when released while still waiting for threshold recording
• Fixed issue where “Cancel Count Ins” action could interfere with overdub layer advance
• Fixed some issues with importing, caused by tempo handling discrepancies
• Fixed pitch bend MIDI messages for Send MIDI action
• Fixed some layout editing issues with text and tutorial widgets
• Fixed some tempo issues when trimming
• Fixed issue where track could go silent briefly when trimming
• Fixed an issue with stopping and playing back a clip with “Pad Loop Length” enabled, immediately after recording
• Fixed issue with overdub feedback handling when trimming
• Fixed issues with selection in sequencer
• Fixed issue with playback of very short clips (after trimming, or importing)
• Fixed issue that could lead to “ghost” control bindings
• Fixed auto loop detection when starting with a pre-set tempo
• Ignore AUv3 render timeouts in diagnostic mode (for debugging AUv3s within LP)

Version 1.1.17

• Added Musical Typing: Use an attached computer keyboard to play an AUv3 instrument
• Added Clip Playhead action: View and adjust playback position of a clip or group of clips
• Added Beats Per Bar action
• Added parameter discovery for MIDI learn when showing plugin UI
• Added “Input Gain” parameter for audio sources, and added “Mute Position” option for audio source mute to enable mute at input (useful for making input effects idle upon mute)
• Added long-press on audio source mute button in mixer to choose mute position
• Added support for restart of the free trial
• Made Audio and MIDI sources ignore each other when soloing via mixer
• Automatically add plugin MIDI destination when adding a MIDI source, if there’s just one candidate
• Fixed issue with MIDI-capable effects not being able to be targeted by Send MIDI action
• Fixed issue switching between “Off” and other MIDI trigger states
• Fixed an issue with play/stop actions occasionally using the wrong quantisation setting
• Implemented partial workaround for loss of keyboard focus when interacting with AUv3s
• Fixed issue with missing clip play/stop notifications, which could prevent follow actions from firing
• Fixed an issue where selected preset sometimes isn’t updated when choosing an AUv3 factory preset while a user preset selected
• Fixed “invert” state for parameter assignment/toggle actions
• Show tempo, metronome and master volume actions for toggle triggers
• Revise phase preservation to work correctly when immediately recording a second clip/performing other actions
• Revised implementation of “Retrigger” feature of play action to fix issue with “Play Once”
• Fixed issue with automatically-muted sources not actually being muted sometimes
• Fixed issue where successive recording and playback stop actions could result in a spurious count-out
• Fixed filting of non-voice MIDI messages when channel filter specified for MIDI destinations

Version 1.1.16

• Fixed orientation with some new projects created in portrait mode
• Fixed some issues with relative CC control
• Fixed clip speed adjustments when time fitting set to “Varispeed”
• Fixed issue with “Send MIDI” actions targeting an AUv3 sometimes no longer working after reloading a project

Version 1.1.15

• Added computer keyboard control support: trigger Loopy Pro’s actions from a computer keyboard, or a device that acts as one
• Added “Beats” units for ramp and fade settings
• Increased minimum retro record buffer to 8 bars
• Fixed sync issues with some MIDI AUv3s
• Fixed Send parameter nudge configuration slider
• Fixed saving of project settings upon save
• Added list of owned features to bottom of System Settings screen

Version 1.1.14

• Implemented separate overdub count in/out setting
• Added “Retrigger Current Value” action for targeting stepped dial/radio widgets
• Fixed crash when starting new project while clip awaiting threshold record
• Fixed issue where loop could fail to play back upon initial record
• Fixed issue with state display of radio widgets
• Fixed issue with “Load Project” follow actions not firing
• Fixed loop re-record incorrectly causing playback to end
• Fixed missing “Toggle” option for “Trigger Widget” action
• Fixed state feedback for “Scroll” actions of radio/stepped dial widgets
• Fixed “Pick Up” parameter issue with some parameters
• Fixed issue with loop drift in certain circumstances
• Fixed a crash during record scheduling
• Fixed a possible hang

Version 1.1.13

• Fixed crash when using wrap around with some nudge actions
• Fixed a text rendering issue

Version 1.1.12

• Added 32 and 64 division options for clip slicer
• Added “Sync Start/Stop” setting for MIDI clock; when off, behaves like Ableton Link sync
• Added “Wrap Around” setting for “Nudge” actions
• Added “Auto-Mute Audio Sources” feature (mute sources that may cause feedback when disconnecting your audio interface), replacing “Reset Audio Source Sends”
• Improved tail recording
• Improved MIDI/Link clock sync, to allow “Phase Preservation” to work correctly
• Improved MIDI Learn for “impulse” CC triggers
• Don’t reset clip volume when clearing
• Fixed an issue with loading projects from saved state when LP is loaded as an AUv3
• Only play loop outro if loop will stop playing at loop boundary (allows immediate stop)
• Perform “Play” follow actions after initial record ends, not when it starts
• Revised playback behaviour to ensure play groups are always respected for solo actions and when targeting multiple clips
• Tweaked startup and route change handling to avoid potential feedback
• Wait for threshold recording to begin before switching one-at-a-time/etc playback
• Fixed a click when transitioning to tail playback in loop
• Fixed an issue with Launchpad/APC40 device discovery
• Fixed an issue where a track that was playing on project load, then cleared and recorded with stop after record, didn’t stop
• Fixed an issue where “Trigger Widget” actions could change when the target widget’s actions change
• Fixed an issue where loop outro might not play
• Fixed an issue where set of playing clips not preserved when toggling playback state of a selection of clips
• Fixed an issue where widget editor screens could become unresponsive
• Fixed an issue with possible click when transitioning to loop outro
• Fixed incorrect initial playhead for non-phase-locked retro record loops
• Fixed “Use Velocity” setting for MIDI control of clip playback
• Fixed some Apple Pencil interaction issues
• Fixed some issues with trimming the initial loop
• Fixed “Assign Value” actions for stepped dial/radio widgets
• Fixed a “Phase Preservation” issue with non-phase-locked loops
• Fixed an issue with duplicating profiles and making successive edits

Version 1.1.9 – 1.1.11

• Added support for input selection (e.g. built-in mic or wired mic)
• Fixed issue with LP AUv3 state loading where project could fail to load from saved state
• Fixed delayed touch interaction on XY pads
• Fixed an issue where trimming initial loop could cause it to go silent briefly
• Fixed double-count-in interval when both clock count-in and loop record count-in enabled
• Added workaround for developer tools bug which caused a crash on iOS 14 and lower

Version 1.1.8

• Added some measures to avoid conflicting workspace accesses when using “Load Project” action
• Added “Previous” options for “Load Project”
• Better Zoom/FaceTime/etc compatibility: Enter playback-only mode when microphone in use by video conferencing
• Don’t disable fade-out if also playing outro
• Improved recursion detection for actions system
• Improved slider interaction
• Revised canvas element selection appearance
• When starting loop record with clock paused and clock count-in enabled, do count-in first
• Fixed an issue where sequencer could behave strangely immediately after “Load Project” action, if timeline loop present
• Fixed an issue with incorrect sequence playback after tempo change
• Fixed extended mixer in landscape on iPhone
• Fixed issue where intro didn’t play (or created a buzz) when starting sequencer from a “Load Project” action
• Fixed issue where undo/redo could be broken when cancelling recording by clearing a clip
• Fixed issue with sequence playback immediately following “Load Project” action
• Fixed missing “Play” follow actions for playing tracks on project load with “Load Project” action
• Fixed numeric input in regions that use “,” or other characters for decimal separator
• Fixed silent first loop when recorded with retrospective recording and loop audio threshold recording on
• Fixed occasional project load issues (including time-stretching weirdness)
• Fixed some crashes

Version 1.1.7

• Added new “State Feedback” setting for widgets, to determine how to display state, based on actions
• Added “Show Color Labels On Clips” accessibility option
• Added “Auto Count Out Overdub” switch for one-shot clips’ recording settings (enabled by default)
• Made some improvements to auto loop detection
• Made “Second Quantization” setting apply to record start, as well as playback actions
• Revised “Solo” functionality to apply to all mixer channels; added Bus Solo action
• Fixed a couple of crashes
• Fixed an issue with initial state display for widgets
• Fixed buzz when overdubbing one-shots
• Fixed decibel slider scale
• Fixed feedback for “Solo” actions
• Fixed incorrect behaviour with “Play” action for a play group when it’s already playing
• Fixed incorrect limit of EQ/Lowpass/etc filter cutoff/center parameters on load
• Fixed initial presentation of “Show Automatically” tutorial widgets on a different page
• Fixed issue where plugin windows could open on their own when switching back to main screen after changing presets
• Fixed issue with audible changes to biquad effect (lowpass/EQ/etc) parameters when returning from idle
• Fixed issue with clip slicer/button grid not working after changing number of buttons
• Fixed issue with stepping through AUv3 user presets
• Fixed issue with updating “Original Tempo” clip setting with keyboard input
• Fixed issue with “armed” sequence playback, where recorded clips were not stopping correctly
• Fixed master volume action scale issue
• Fixed issue with “Input Gain” parameter range

Version 1.1.6

• Added Multiroute Audio, for using built-in headphone port and USB audio interface simultaneously
• Added support for Bluetooth advertising (advertise device as Bluetooth peripheral)
• Added ability to rename MIDI sources
• Added labels to color swatches in editor
• Added support for multiple metronome outputs
• Made “Nudge” action for Speed and Rate multiply rather than add (e.g. Nudge 0.5 will halve, 2 will double, -1 will toggle between forward and reverse)
• Enabled Copy for actions within Control Settings section
• Improved MIDI Learn: Now does better at recognising and adapting to incoming trigger types (continuous versus impulse)
• Improved MIDI trigger selection screen, to facilitate changing trigger types
• Revised keyboard layout slightly and added octave navigation buttons
• Revised square count-down layer to be linear
• Show count-in/out on clips when playing intro/outro, and show intro/outro playhead on waveform in clip screen
• Update any pre-set loop durations to correctly reflect changes to time signature
• When using a continuous control to adjust a stepped dial/radio, only perform actions when index changes (prevents spamming the action, which can cause issues like skipping quantization delay)
• Round loop durations to whole numbers of beats, if they are slightly out, to address potential drift issues
• Revised binding execution to always begin from the first action when triggered rather than continuing from last position if cancelled
• Made some small adjustments to clip scheduler to avoid conflict between play toggle on press, and solo on hold/double-tap
• Fixed a number of glitches with overdub feedback
• Fixed a possible crash when switching pages
• Fixed a potential crash when loading an old project
• Fixed issue with saved time-scaled audio, when LP loaded as AUv3
• Fixed issue where overdub might fail if tail recording enabled
• Fixed issue where sequence-armed loop wouldn’t stop at end of sequenced segment
• Fixed issue where “Auto Count-Out” didn’t take effect for the second loop recorded, if started immediately after first
• Fixed issue with OSC not working with global profiles
• Fixed issue with actions not being performed after parameter ramps
• Fixed potential issue with Play/Stop follow action execution
• Fixed issue with triggering widgets with quantized/delayed actions
• Fixed pops when changing loop playback state while paused
• Fixed some memory leaks
• Fixed some performance issues
• Fixed an issue with mouse scrolling

Version 1.1.5

• Added individual retrospective record length setting for actions, clips, colours and globally
• Added “Invert” option for toggle actions
• Added “Preserve Clock” setting to clear clip action settings
• Added OSC support for delay/quantisation of actions via +nn/~nn parameter
• Added a workaround for AUv3s that don’t correctly report their selected presets
• Added “Compressed” file format option (uses m4a/aac)
• Improved faders, mapping more of the travel distance to middle decibel ranges
• Made colour channel volume meters post-fader, rather than pre-fader
• Automatically reload a crashed AUv3 (with 5 second rate limit)
• Improved quantization setting sliders, to allow other bar lengths
• Improved intro and outro playback
• Improved AUv3 preset actions
• Improved “Loop” quantisation for Page Switch actions
• Improved recording of irregular-length loops when quantisation enabled
• Revised trim interaction
• If clock tempo is unset when playing a clip, set the tempo
• Fixed a number of memory leaks
• Fixed a spurious count-out indication that could start upon playback
• Fixed an issue related to entering a sequencer loop region, which could cause odd events to fire, including sending loops silent
• Fixed an issue where audio system could go silent when multiplying/dividing a clip
• Fixed button grid widgets not working immediately after creation
• Fixed issue where playing one-shots could replay from start when unpausing clock
• Fixed issue with clip slicer with clips with only one transient
• Fixed issue with update of font size on button labels
• Fixed issue with “Play Once” sometimes not working properly
• Fixed some crashes
• Fixed some glitches post-record
• Fixed a couple of issues that could cause glitches during overdubbing
• Fixed artefacts during overdubbing with overdub decay less than 100%
• Fixed “Loop” quantisation sometimes not taking effect
• Fixed issue with sequencer playback offset into clips when tempo of clips doesn’t match project tempo
• Fixed session recording finalise on app termination
• Fixed handling of delete/rename/move of loaded projects which are marked as templates

Version 1.1.4

• Many stability fixes and rendering improvements
• Added “Recently Deleted” area for staging deletion from file browsers
• Fixed problem with AUv3s dropping MIDI output/transport sync when reconfiguring

Version 1.1.3

• Implemented collapsible mixer sections
• Allow wider vertical zoom in sequencer
• On load, set sequencer zoom to show whole sequence
• Fixed issue where scroll layer contents could become unresponsive after zooming
• Fixed sequence layer content height calculation (was chopping off the bottom)
• Fixed update of mixer layout when a section expands
• Fixed issue with hit testing which, among other things, broke bottom trigger area of MIDI learn popover
• Tweaked clip slicer transient detection
• Fixed issues with “toggle” parameter actions
• Fixed some crashes

Version 1.1.2

• Added Loop Peel/Replace action, for undoing and redoing layers
• Added support for “xx” value placeholders in custom Send MIDI continuous actions (e.g. for controlling SysEx messages via a slider, for coarse/fine CC controls, etc)
• Added editable fader/balance labels to mixer
• Made some significant UI optimisations
• Tweaked clip slicer algorithm to trim trailing silence
• Improved selection gesture in canvas editor
• Revised mixer layout to address UI issues with large numbers of destinations/sends
• Replaced Link “Force Tempo” setting with “Act as Master”, which also enables immediate playback start
• When sorting sequencer tracks by colour, use mixer order
• Removed dragging mechanic for play group assignment, in favour of marquee selection
• Fixed clip slicer triggering while loop is playing
• Fixed fade out
• Added preset state workaround for AUv3s that don’t report their selected preset
• Fixed crash related to triggering parameters when hosted as AUv3
• Don’t wait for playback start when a recording a one-shot
• Improved interaction within scrolling areas

Version 1.1.1

• Added “Continue Playback From Slices” option for clip slicer
• Added support for Pitch Bend messages with “Send MIDI” action
• Added sort by timeline position for sequence tracks
• Added “Force Tempo” option for Ableton Link
• Moved Fade In/Out settings into main clip settings area
• Fixed issue with clip intro playback in sequencer
• Fixed issue where a “Play Once” loop didn’t stop properly
• Fixed sequencer vertical scrolling when zoomed
• Fixed issues with export from sequencer
• Fixed some microfade issues that could cause lost transients on one-shots when fade in is set to “hard zero”
• Fixed fade-out duration for one-shots
• Fixed issue with missing quantisation when triggering widgets with quantised actions via MIDI/etc
• Fixed issue with clip slicer and speed/rate/tempo variation
• Fixed issue where pasted clips could fail to play back immediately
• Fixed slider title colouring
• Fixed issue with reverse clips in sequencer
• Fixed incorrect MIDI feedback state values when first reported after load/creation
• Fixed missing control feedback for clip slicer/button grid
• Revised radio/stepped dial behaviour: Don’t update position when individual items’ state changes
• Fixed a number of crashes

Version 1.1

• Added Varispeed & Reverse playback
• Added Time Fitting settings: Time Stretch, Fast Time Stretch, and Varispeed, and None
• Added Stepped Dial and Radio widgets *
• Added overdub feedback control *
• Added Audio source and MIDI source replacement, with long press on icon in mixer *
• Added support for multiple simultaneous control profiles *
• Added ability to seek to particular sequencer sections (absolute or relative) using Clock Seek action *
• Added Phase Align action *
• Added OSC support *
• Loopy Pro AUv3 additions: multi-inputs and outputs *
• Loopy Pro AUv3 additions: MIDI input and output, and custom parameter support
• Added support for overdub after retro record
• Added new control profile actions
• Added new Tutorial widget
• Added new “Pad Loop Length” behaviour
• Added global follow actions, and follow actions for project load, page switch, and start/stop clock
• Added began/ended initial record and overdub clip follow actions
• Added copy/paste and duplicate for actions, on long-press
• Added copying control profiles between project and global
• Added double-tap action for XY pad widget
• Added LP-707 sample project by Inkie
• Added mouse scrolling and right-click support
• Added per-clip input gain parameter
• Added search bars in new effect/source screens, action directory, and file managers
• Added support for driving the MIDI Control system from any AUv3 MIDI source
• Added “All Clips” option for parameter actions
• Added separate “Microfade” and “Hard Zero” settings for fade in/fade out, to disable all microfades if necessary
• Added support for “This Clip” target for follow actions
• Added settings for merge gesture
• Added switch for default tap action to disable, in gesture settings
• Added “Begin Overdub If Recording” option for record actions
• Added “Clear Target” option for merge action
• Added “Start Clock If Paused” option for playback actions
• Added undo/redo through each separate overdub layer
• Added font size/text alignment settings for button widgets
• “Record Start” action can now close loop and immediately enter overdub
• Enable multiply/divide while overdubbing
• Improved behaviour of action sequences, when retriggering during a count-in delay
• Remember mixer scroll position
• Revised file managers: show empty folders, added create folder button, and rename on long-press
• Added separate “Play” and “Stop” quantization settings
• Updated Set Master Length action to add “Copy from Clip” mode, and arbitrary “Scale” mode
• Master volume and metronome volume actions can now go up to 24dB
• Multiple characters for page names
• Added “Clear” function for device bindings in control profile editor
• Added Enable Network MIDI setting (now disabled by default, due to iOS bugs with Network MIDI)
• Added automatic clip mix-down after reaching a threshold number of overdub layers
• Added sort function for sequencer tracks
• Many, many performance optimisations and other improvements

* Additions marked with a “*” are paid upgrades: If it’s been more than 12 months since you purchased Loopy Pro, unlocking these will require a one-off in-app purchase, which will also unlock any new features released over the following 12 months. Upgrading will help me keep working on Loopy Pro for years to come. See loopypro.com/pricing for details.

Version 1.0.42

• Respect play group rules when targeted by play actions
• Fixed widget actions in global control profiles
• Tweaked mixer layout on smaller screens
• Fixed “Next Selected Color” for parameter actions
• Tweaked “Loop” play quantisation with stopped, phase-locked loops to work better if loop is offset
• Fixed “Play Once” loops not playing after offsetting or editing

Version 1.0.41

• Fixed issue with intro recording when overdub-after-record is enabled
• Fixed a potential crash when copying/pasting
• Fixed waveform update after rotation
• Fixed a couple of issues with AUv3 user presets
• Fixed potential crash when an AUv3 crashes
• Fixed possible glitch on initial loop playback
• Fixed issue with excessive timeline seeks with jittery clocks when hosted as an AUV3

Version 1.0.40

• Made “Selected Clip” page-specific, so it persists when switching pages
• Fixed count-out duration issue with intro recording
• Fixed loop intro playback upon timeline start, when phase lock is disabled
• Fixed a potential click when transitioning from intro to main loop
• Fixed issue where clip merge could be recognised on drag, even when disabled
• Fixed effect idle mode setting synchronisation across instances
• Fixed a mixer layout glitch when switching from edit screen
• Fixed issue with audio unit actions in global control profiles
• Fixed sequence selection outside of viewport

Version 1.0.39

• Optimisations for MIDI control system, especially performance improvements for MIDI Learn UI
• Fixed glitchy audio with newly-recorded loop when in a group with pitch- or tempo-adjusted loops
• Fixed a potential crash during un-quantized recording
• Fixed an issue with un-quantized overdubbing where layers could go missing
• Fixed crash when cancelling record of a loop in a pitch- or tempo-adjusted colour
• Fixed a potential a crash/memory leak when deleting a page
• Fixed a potential crash when deleting clips
• Fixed an AUv3-related crash when restoring after being suspended in the background
• Added a safety measure for validating purchase, in the event of an App Store failure
• Added support for “Second Quantisation” for Load Project action, and fixed count-in calculation with custom quantisation
• Set “Retrigger on Play” for row/scene actions on APC40mk2 and Launchpad

Version 1.0.38

• Added some layout optimisations to improve switching between edit mode and back
• Added optimisation to speed up deletion of multiple canvas items at a time
• Added increased memory limit entitlement
• Fixed some issues with sequence export
• Fixed an issue with non-seamless loop export
• Fixed some issues with cross-project transitions using Load Project action
• Fixed some memory leaks
• Fixed a potential crash when deleting clips targeted by actions

Version 1.0.37

• Fixed issue with final overdub layer being removed upon ending overdub

Version 1.0.36

• Added “Loops play independently” mode for play groups
• Added “State Saving” options for Audio Unit: Save whole project, or just project reference (to avoid memory issues with huge projects)
• Added Link phase indicator to clock/tempo button when not running
• Empty tracks (colours, with no clips in them) will now load presets properly, do monitoring thru, etc
• Increased max retro record buffer duration
• Fixed pick-up controller mode
• Fixed some memory leaks that could cause app slowdown after a while
• Fixed an issue with “Remember playback state” option for play actions
• Fixed a waveform analyser issue causing slow display
• Don’t send MIDI feedback after just receiving corresponding message, to avoid jitter
• Tweaked relative CC detection
• Apply Phase Correction after loop recording even when Length Quantization off, when appropriate
• Fixed some glitches associated with “Round to nearest BPM” setting
• Fixed spurious MIDI/Link clock start when tapping tempo/etc
• Fixed missing “Stop” follow action for one-shots, when reaching end of playback
• Made “Ignore Timestamps” the default for MIDI controllers
• Fixed Launchpad/etc colours for bound widget actions
• Fixed a couple of intro recording issues
• Fixed timing inaccuracy with consecutive sequencer segments when first segment causes record
• Fixed issue where armed sequence tracks could stop too soon during playback

Version 1.0.35

• Fixed issue where auto loop detection could engage during session

Version 1.0.34

• Fixed a MIDI clock sync receive issue that could cause jumps
• Fixed some issues with armed recording sequence start
• When “Record on Press” in use, show clip about to record in red, on press
• Added timeout for record on press

Version 1.0.33

• Added a workaround for some MIDI AUv3s sending incorrect MIDI times
• Fixed issue with divide on transients for clip slicer

Version 1.0.32

• Revised bottom-left navigation buttons in edit mode
• Fixed an issue in MIDI clock receiver which could cause jumps
• Fixed visual loop state update when toggling Phase Lock or when changing timeline while loop disabled
• Fixed “Count-In Only” metronome mode
• Fixed issue with “Retrigger” setting for play action
• Minor optimisation for faster project loads
• Optimisations for sequence screen

Version 1.0.31

• Fixed re-record count-out
• Fixed metronome flash when counting-in
• Fixed incorrect offset of phase-locked loops when recorded with an armed sequence and offset against loop boundary
• Fixed issue with one shot playback when pausing clock
• Fixed a couple of potential crashes
• Fixed issue where exclusive double-tap MIDI actions could stop on-press actions

Version 1.0.30

• Fixed issue with quantisation sliders below 1 bar
• Allow running timeline when synced to a stopped MIDI clock source
• Fixed a couple of recording issues
• Improved waveform display for drone loops
• Fixed slider/dial widget values when partial controller range applied

Version 1.0.29

• Added Toggle/Start/Stop/etc options for pause/unpause action
• Added “Retrigger” option for already-playing loops in play/solo action
• Added “Round to Closest BPM” setting for tempo detection
• Fixed occasional issues with loop phase correction after recording
• Fixed incorrect record count-in behaviour when using “Wait for Playback” (should be no count-in)
• Fixed cross-project-transition issue where sequenced project could continue playing
• Fixed issue that could cause auto-detected loop tempo to exceed specified detection range
• Fixed issues with unstable MIDI clock output
• Fixed a rare crash in playback

Version 1.0.28

• When putting instrument audio units into idle mode, clear MIDI notes and audio decays
• Improved mixer solo implementation
• Added hide/show and enable/disable buttons to long press popup on effect icons in mixer
• Fixed issue with sending MIDI to MIDI-capable effects
• Fixed some potential issues on project load
• Fixed a possible crash when using “Wait for Playback”
• Added missing disable-effect-with-decay feature to effect toggle buttons on mixer and AUv3 window toolbar
• Fixed issue with opening exported controller profiles
• Fixed clock seek action when using non-phase-locked loops
• Fixed issue with undo action on hold/double-tap, when alongside tap to toggle record (as on some hardware loopstations)
• Fixed incorrect loop offset in sequencer when recording non-phase-locked loops from a stopped timeline
• Fixed some issues with multiply/divide
• Revised decay end trigger when disabling effects, and added a 10s timeout in case effect doesn’t go silent
• Fixed issue where cancelled tail recording could cancel whole loop record
• Fixed issue that could break undo/redo when clearing a clip
• Fixed file renaming in App Extension folder
• Only apply audio source send reset if bus has route to output
• Fixed some MIDI clock send issues, particularly when synced via Link
• Fixed phase locked loop playback with time stretching disabled
• Fixed disappearing AUv3 windows on device rotation, and associated AUv3 crashes
• Tweaked glid slicer playback of even subdivisions
• Fixed crash when playing back using slicer with a loop crossfade duration of zero
• Fixed spurious audio input when LP is hosted as an instrument AUv3

Version 1.0.27

• Fixed playback issues with clip speed slider
• Fixed issue with New MIDI screen mixing up AUv3s with the same manufacturer/subtypes
• Improved clip length slider
• Fixed potential incorrect clock phase offset at end of loop record when simultaneous record in use
• Disable renaming if not allowed by iOS (e.g. opened project from Files)
• Block iOS 16 3-finger editing gesture

Version 1.0.26

• Added “Seek Timeline” action
• Fixed issue with multiple XY pads addressing the same AUv3 instance
• Added instrument and MIDI AUv3 parameter support to XY pads
• Improvements to Ableton Link outward sync when recording first loop or bridging from incoming MIDI clock
• Improved filenames when exporting recordings
• Improved tempo estimate for imported files
• Added UI to re-join Link tempo after clock tempo has been reset
• Added more stopping points to quantization slider
• Fixed issue with free loops coming in at incorrect position after clock count-in
• Fixed loop alignment issue when using overdub-after-record mode
• Fixed zipper noise when adjusting volume sliders
• Fixed a crash when loading some projects
• Fixed an issue with “Finish Record” follow actions on the first loop that sets the tempo
• Fixed issue with sequence recording of ‘stop’ play actions being interpreted as ‘play’ action
• Fixed audio artefacts when removing the only send to a bus
• Fixed “Combined Input” recording with non-monitored sources
• Fixed issue with stuck notes when muting MIDI sources
• Fixed a possible crash when setting buffer duration
• Fixed a crash which could occur when switching projects with MIDI sources
• Fixed issue with tempo slider randomly entering fine adjustment mode
• Fixed a number of memory leaks
• Fixed a rare crash when auto-saving with AUv3 effects

Version 1.0.25

• Revised mutually-exclusive play group implementation for greater flexibility
• Enabled “All Loops” solo context to apply across all pages in project, not just current one
• Addressed issue where undo/redo may become disabled after cancelling a recording
• Fixed audio phasing issue when incoming MIDI clock is a little unstable
• Fixed excessive seek crossfade when using clip slicer
• Fixed some play group outline visual glitches
• Fixed laggy AUv3 window movement
• Fixed a number of issues with tail/outro playback, and with overdub layers
• Fixed issue where short loops could stop immediately instead of doing outro/count-out
• Fixed some issues with shorter loop fade-out settings
• Fixed possible glitch on initial loop playback start
• Fixed crash when using ‘multiply’ action
• Fixed issues when hosted as an instrument in GarageBand
• Fixed issue with degraded initial loop audio when recording first two loops consecutively
• Fixed some clip waveform rendering issues
• In AUv3 windows, require tap directly upon pencil icon to edit audio unit name, rather than anywhere on titlebar
• Fixed a number of potential crashes

Version 1.0.24

• Fixed potential save error when saving from within AUv3
• Fixed a crash when playing across end of sequencer timeline loop boundaries

Version 1.0.23

• Added new “Save Session” action
• Added “Save As New” option to Load Project action
• Fixed live time-stretch errors with non-phase-locked clips
• Fixed issue where monitored inputs were doubled in “Combined Input and Output” recordings
• Fixed AUv3 keyboard state save
• Fixed some crackles and pops associated with loop boundaries of successive overdubbed layers
• Fixed a glitch that could occur after initial loop recording with some audio interfaces
• Fixed “Play Once” setting not being respected on initial clip playback upon loading project
• Tweaked clip waveform display to better handle loop boundaries
• Fixed MIDI hardware support in LP AUv3
• Fixed issue with logarithmic parameter curves
• Fixed an issue where dragged items might become rearranged unexpectedly after dragging
• Fixed incorrect change to clip “Original Tempo” setting when turning off time-stretch
• Fixed issue with resizing of canvas to accomodate pasted items
• Fixed rendering of play group outlines, with some geometries
• Added missing copy of resources from clip tail and intro, when copying
• When reconnecting MIDI destinations, fall back to matching on name if unique identifier match fails

Version 1.0.22

• Fixed delays due to interaction between play and record actions on tap and double-tap or vice versa
• Fixed incorrect playback duration for armed loops in sequencer
• Fixed “Send MIDI” action Program Change value issues
• Fixes a crash when triggering record from a swipe gesture

Version 1.0.21

• Fixed an issue where loops may offset incorrectly after record, if time stretch disabled
• Fixed an issue where phase lock may not work in loops at the master tempo, if time stretch disabled
• Allow sub-bar timeline realignment after loop record (e.g. record 2 initial beats, then timeline will start at bar 2 afterwards, as expected)

Version 1.0.20

• Fixed an issue with MIDI control when hosted as an AUv3
• Fixed an issue with preset loop length slider refusing to go to “Unset” state at some time signatures

Version 1.0.19

• Enable phase lock for non-time-stretching loops that match the current clock tempo
• Fixed missing transients at beginning when retriggering oneshots
• Fixed a memory leak

Version 1.0.18

• Improved latency/lag with record start/stop:
  • Implemented immediate record stop from audio thread, to reduce interval until initial audio playback
  • Added “Ignore Timestamps” option for MIDI devices, which can reduce lag with some configurations, at the expense of possible timing jitter
  • Fixed issue where loop rotation/circle gesture interferes with record timing when “Record On Press” on
• Improved time-stretching logic and track tempo management
• Full drag/drop rewrite for improved importing and better workflow with multi-file drops
• Added “Loop Boundary Crossfade” setting
• Added recording action option: “Preempt Other Actions” (on by default, matching prior behaviour)
• Improved clip screen tempo controls (and hide them when time-stretch disabled)
• Made “Play Target” option for merge/move action three-phase: Never, If Source Playing, and Always
• Increased max fade duration to 120 seconds
• Fixed crashes associated with EQ/Lowpass/Highpass/Bandpass/etc modules
• Fixed file browser crash
• Fixed click at first loop playback when overdub-after-record in use
• Fixed loop boundary crossfade for imported loops
• Fixed loop outro, when setup via trimming in clip screen
• Fixed intro playback for non-phase-locked loops
• Fixed a glitch when transitioning from intro to main loop
• Fixed clip analyser issues when time-scaled
• Fixed initial clip fade-in
• Fixed issue with stopping one-shots by colour
• Mute all incoming MIDI from muted sources, not just notes
• Copy clip gestures too, when copying
• Added some missing clip property assignments, when copying
• Update non-phase-locked clips’ phase too, when making MIDI Clock/Link phase corrections
• Fixed clip waveform analyser when offsetting backwards
• Fixed some assorted crashes when adjusting clip boundaries
• Fixed floating-point error issue when fading in, which could result in permanent fading-in state
• Fixed skip back to beginning of clip when tapping again to abort fade-in
• Fixed “tap” gesture actions on oneshots
• Fixed spurious count-in if a loop has intro disabled
• Don’t try to time-stretch when dragging to import, if stretching disabled
• Fixed an issue where playback could fail after time-stretching
• Added diagnostics to support email when tapping email address in Help
• Don’t try to set nonsense clip titles when dragging files into LP
• Fixed a number of memory leaks
• Cleaned up some initialisation inefficiencies

Version 1.0.17

• Fixed issue where overdub layers could be offset incorrectly post-record
• Automatically stop session recording if app terminates or suspends in the background
• Attempt to recover unfinished session recordings on startup
• Fixed cleanup of old temporary files on launch
• Do clock phase shifting for non-phase-locked loops too, as long as phase shift is on

Version 1.0.16

• Fixed playback of initial loop when “Wait for Playback” is enabled
• Fixed undo/redo issue when recording second loop immediately after initial one
• Fixed issue where clock could pause after initial loop if loop threshold recording on at global level, but off at clip level
• When trimming a recording, offer to make a copy or trim original, instead of always trimming original
• Improved automatic loop detection with already-tight loops
• Fixed reset clock tempo when there are one-shots present
• Fixed non-phase-locked loops not beginning playback correctly after redo
• Fixed sequence recorder issue creating spurious segments for already-present segments when starting record
• Fixed rounding/snap of sequence layer segment endpoint when dragging
• Fixed overdub count in/out when “Loop” quantisation setting used
• Reset loop playback offset when cleared
• Fixed issue where offset tracks may not reset phase correctly on clock pause when idle
• Fixed sequencer segment dragging when at max zoom level
• Memory leak fixes

Version 1.0.15

• Fixed issue with first loop alignment in some cases
• Fixed issue with stuck notes if multiple consecutive note ons received
• Fixed issue where turning off playback/recording settings at group level then saving does not persist
• Fixed slider value assignment when editing using keyboard (long press/double-tap on label)
• Disable initial record count-outs with “Loop” setting if Length Quantization is off

Version 1.0.14

• Fixed issues with Phase Correction when Phase Lock on
• Fixed an issue with bindings with long chains of actions
• Fixed hold/double-tap interfering with record on tap
• Fixed some issues with undo/redo when recording
• Fixed slider widget gesture direction when square aspect
• Fixed a “lengths are too different” error for track merging
• Tweaked AUv3 parameter assignment to avoid crashes in some AUv3s

Version 1.0.13

• Added “Phase Preservation” recording setting, which controls whether or not LP will rotate a new loop to align the start (on by default).
• When on, loops will now reliably maintain the phase with current playing loops
• Added “Loop” mode for record count-in/out quantization setting
• When counting-out record with no count-in, count out based on recording length rather than clock position
• Added “Auto Count Out” setting for one-shots (in clip details screen, or via actions; off, by default)
• Added title field to clip details popover, visible above waveform after pulling up
• Added double-tap or hold on value label on any slider to open text field
• Added support for one-shot playback quantisation using UI
• Set clip title to filename on import of audio file
• Fixed post-record initial loop playback delay when auto loop detection is on
• Fixed a save points issue with large AUv3 save state, where only latest save state was kept
• Fixed a project save issue that could result in missing AUv3 saved state
• Fixed second tap to stop current fade-out and stop immediately
• Fixed layer progression error with overdub on a hold action
• Fixed X-Y pad mapping reset issue when reloading projects
• Fixed white sequencer segments
• Fixed some one-shot overdubbing issues
• Allow MIDI trigger holds and double-taps resulting in a record toggle to pre-empt taps and perform immediately, to avoid delays
• Remember metronome on/off state when saving projects
• Revised EQ/Lowpass/etc node UI to hide callout when ending drag, rather than showing larger callout
• Fixed conflict issue with overdub-after-record and tail recording
• Stop recording non-hold-to-play one shots on release, not on press
• Restart timeline to beginning on MIDI clock stop
• When overdubbing a playing one-shot, disable audio threshold record start
• Fixed count-ins when using clock “Perform Count-In” setting
• Enable record count-in for “hold to record” actions
• Fixed stuck on/highlit loop state when using “Wait For Playback” and count-in, and stopping clock before count-in ends
• Improved count-in/out display indication to reflect actual delay interval
• Fixed a possible crash on paste
• Fixed issue with clip exporter if project, group, or clip name contains non-filesystem-safe characters
• Fixed a possible crash during recording
• Some optimisations for directory listing with large folder structures
• Fixed crash when opening initial loop edit screen after recording empty audio source
• Fixed incorrect step size for “MIDI Controller” AUv3 parameter unit type
• Fixed memory leak of pre-fader effects on master output channel when starting new projects
• Revised AUv3 parameter value update to use different iOS AUv3 API mechanism: prior one was buggy and caused hangs. This should fix a lot of hang crashes when using AUv3s.
• Moved AUv3 allocation to background thread to avoid possible hangs due to AUv3 bug

Version 1.0.12

• Added support for “Pause Clock When Idle” when finishing recording a track in stop-after-record mode
• Include “Monitor Through” signals in level analysis for colours
• Reset “Pick Up” controller state when underlying value is changed substantially
• Added “Mute Speaker Beside Mic” setting to System Settings (for iPhone only; on by default)
• Fixed fractional clock lengths for Set Master Length action
• Sped up directory scanning in Projects screen
• Fixed issue with APC40mk2 automatic bindings re-establishing on project load even if disabled
• Added app version number to bottom of system settings screen
• Wait for finish of save process when terminating app
• Fixed remnant IAA info panel after removing using delete button
• Fixed issue with Link count-in with un-phase-locked loops
• Tweaked clock count-in to fix missing downbeat of metronome count-in

Version 1.0.11

• Added global AUv3 icon cache for faster loading
• When identifying phase of recorded loop, use longest playing loop, rather than longest loop for phase master
• Fixed navigation with MIDI receiver settings screen
• Launchpad support: treat MK3’s “DIN” port as generic device
• Fixed out-of-bounds value for master volume action
• Fixed incorrect update of clock tempo when causing record end by pausing the clock
• Only preempt ‘clear’ actions (on additional hold/double-tap binding) from play/record actions
• Fixed a record start/stop timestamp handling issue that could result in incorrect timing
• Added some help tips about global control profiles (see also Profiles)
• Fixed issue with sporadic feedback monitoring of AUv3 parameters
• Fixed a crash when rapidly toggling AUv3 windows

Version 1.0.10

• Ableton Link sync improvements
• Fixed an issue that could cause some widget buttons to become unresponsive
• Fixed issue with action chaining for play actions that cause record start
• Fixed mute action when targeting colour of next/previous tapped clip
• Addressed glitches on some hardware at certain sample rates
• Allow exclusive group recording with stop-after-record mode to stop playing clips in other groups
• Allow exclusive group playback to stop recordings in other groups when stop-after-record mode in use
• Fixed “Next Tapped Clip” target for record action
• Support for IAP refund + subsequent re-purchase

Version 1.0.9

• Implemented actions for selecting AUv3 presets
• Added MIDI source actions (mute, solo, gain, and all AUv3-related actions)
• Added “Copy Levels” option to Load Project action (to copy all mixer channel levels to new project)
• Added support for connecting MIDI controllers through a secondary hub/wireless adapter: Implemented SysEx Universal Device Inquiry to identify MIDI devices not directly connected via
• USB, and added option to manually select device type
• Added SysEx/custom MIDI string support for Send MIDI action
• Added “Save” button to update existing presets
• Made loop analyser more robust when analysing loops that are already reasonably tight
• Improved AUv3 keyboard layout on smaller screens
• Fixed tempo estimation issue with auto loop detection
• Fixed MIDI sync receive issues with some devices
• Fixed send adjust actions for sends beyond 10th
• Revised app icon and launch screen
• Added MIDI learn for select preset actions
• Fixed an AUv3 state restore issue associated with AUv3s missing parameter change notifications
• Fixed error in AUv3 preset assignment on load
• Fixed issue with passing SysEx messages to AUv3s
• Fixed issue with using “Selected Clip” source/target with merge action across different pages
• Fixed missing “This Clip” option in clip merge/move action, for gestures/follow actions
• Fixed missing “Next Tapped Clip” target for merge source
• Enabled page switching while prompting for tapped track
• Fixed crash when selecting built-in effect presets for preset action
• Fixed issue with no-quantization play/stop action being overridden by clip intro/outro
• Fixed possible click when switching projects
• Fixed mixer layout issue when adding a send + bus
• Added a workaround for audio timestamp jitter from audio system, causing audio artefacts

Version 1.0.8

• Added support for count-in on main playback
• Added support for exceptions for Solo action for all targets
• Added “Panic” and Hide/Show buttons to audio source settings screens
• Added long press on IAA icon on mixer to show settings screen
• Added option to show system status bar (in system Settings app)
• Added mouse cursor interaction
• Allow maximum value for volume parameter actions to be set above 0dB
• Fixed incorrect quantisation on clip start after a merge/move action
• Fixed playback scheduling issues when triggering retro record
• Fixed issue with MIDI sources that also take audio input
• Fixed an issue where orphaned play groups aren’t removed
• Fixed parameter action binding with multiple instances of the same AUv3 audio source
• Fixed “Remember Playback State” issues for play actions
• Fixed MIDI/Link sync issues on pause/play
• Fixed issue with CC Pick Up at ends of range
• Revised playback action interaction with other gestures (like hold/double tap): Always wait, unless it’s a “Clear” action

Version 1.0.7

• Added “Cancel Count Ins/Outs” action
• Added selection shortcuts to “Specific Clip” selector (“Select Playing Loops”, “Select Filled Loops”, etc)
• Added configuration to select between Quantization and Delay timing modes for actions
• Added workaround for AUv3 hosts like GarageBand that don’t send proper audio timestamps
• Added MIDI device configuration, with ability to disable MIDI feedback feature (now off by default for the Morningstar MC8, which had issues with this)
• Respect clip fade in/out in sequencer
• Revised playback to catch initial impulse on first loop after recording
• Stop clip recording when stopping playback as well
• When toggling clip currently playing in clip slicer, start normal playback rather than stopping
• Allow “Pause Clock When Idle” while Ableton Link in use
• Fixed “Switch Control Profile” actions
• Fixed double-tap on window titlebars to toggle fullscreen
• Fixed “Next Tapped Clip”, “Color of Next Tapped Clip”, “Play Group of Next Tapped Clip” targets for some actions
• Fixed issue with missing options for “Next Tapped Clip” for some actions
• Improved “Finish Record” follow action behaviour and timing
• Fixed some issues with AUv3 state restore
• Enabled playback scheduling even if clips to play are all empty (e.g. switching to empty row via solo action)
• Fixed “Play Once” setting when triggered from actions
• Make “Play Target” option for merge/move action respect Play Group settings
• Fixed missing MIDI Learn UI for some widgets when using global profile
• Fixed play sync issue when starting an un-phase-synced loop while recording another
• Fixed clip playback issue when unpausing which could miss transients at start of clip
• Fixed cut-off start of clips when playback triggered from some actions
• Fixed “Stop After Recording” mode

Version 1.0.6

• Added project templates
• Added exceptions list for “Solo” actions
• Added support for 32 frame hardware buffer duration/latency
• Improvements to playback scheduling when targeting multiple clips across different groups
• Improved co-existence of tap and double-tap/hold actions (eg. make record on tap wait for double-tap/hold)
• Added support for cancelling waiting load project action by tapping button at top left
• Save configuration for special devices (in MIDI Control screen) with each project
• Fixed a rare project save error
• Fixed some minor audio playback issues
• Fixed issue copying offset/rotated loops to one-shots, causing silent regions
• Fixed crash when disconnecting MIDI controller with current flash animations
• Fixed initial playback of record-armed clips in sequencer
• Don’t truncate loops with a pre-set duration when ending recording early (pad with silence instead)
• Permanently mute all clips when transitioning away from project, to avoid accidental restarts of clips
• Fixed double-downbeat when using Load Project to switch to project with active sequence
• Fixed issue with missing MIDI clock start when loading new projects with auto-clock start
• Fixed deleting projects from set lists

Version 1.0.5

• Added seamless crossproject transitions and set lists, with configurable crossfade and effect tails, via the “Load Project” action.
• Added MIDI Fighter Twister support with colours and perloop playhead animations.
• Added Audio Source AUv3 parameter actions
• Added a secondlevel quantization interval, invoked when cancelling a countin (see “Second Quantization” in clip settings)
• Added “Toggle” action variant for parameters, to switch between two fixed values
• Added full support for crossproject session recording
• Added “Individual Buses” support for session recording
• Added project title to toolbar
• Added ability to rename audio source channels
• Added MIDI learn hotspots to effect buttons in mixer
• Added effect parameter action to MIDI learn hotspot for effect buttons on mixer and bottom bar
• Added Absolute/Relative settings for CCs in trigger setup for manual configuration
• Added green metronome flash on downbeat
• Added “Reset Audio Source Sends” system setting
• Reset APC40 cursor when changing page or project
• Fixed some initialisation and load issues with AUv3
• Fixed delays when loading file managers with large numbers of items
• Fixed some interaction issues with play group edit screen
• Fixed individual input session recording when multiple inputs present
• Fixed oneshot playback velocity for APC40mk2
• Fixed crashes and issues with audio units when switching/transitioning projects
• Fixed armed sequence launch crash
• Fixed a rare crash when changing audio route
• Fixed issue with saving imported projects
• Fixed some effect parameter action issues
• Fixed some session recording playback screen issues
• Fixed default relative CC adjust speed
• Tweaked relative CC detection
• Fixed issues with audio source balance
• Fixed MIDI Learn hotspot initial state update
• Fixed crash when an IAA audio unit registration has no title
• Fixed crash when encountering invalid Core MIDI endpoints
• Fixed glitches introduced when truncating a clip
• Fixed playback issue that could cause high power/CPU consumption
• Added workaround for audio interface unique ID resetting over reconnections
• Revised postrecord loop phase correction: only perform phase realignment if there are no other loops of same length or longer
• Fixed possible race condition which could cause some crashes
• Added AU instance number to MIDI action targets
• Fixed MIDI action targets selection
• Fixed potential crashes when saving effects
• Fixed missing AUv3 effects in sequence export, and a few other export issues
• Fixed crash when setting clip playback rate to very small numbers
• Fixed issues with record action chaining
• Fixed consecutive clip play/stop action issues
• Fixed an issue with pitch/speed reverting after background process if using sample rate greater than 48k
• Fixed missing AUv3 state in project export
• Fixed user preset saving for AUv3s with spaces in their AudioComponentDescriptions (eg. Beathawk)
• Fixed clock controls screen when heightconstrained (added scrolling)
• Fixed missing audio unit delay line reset (e.g. on enable/disable)
• Fixed missing initial downbeat when receiving MIDI clock
• Fixed saving of custom record configuration for play actions
• Fixed a number of issues with Ableton Link start countin
• Fixed issues with remaining loop phase lock override when disabling sequence
• Fixed recording trimming
• Tweaked canvas editor interaction: tap and hold will bypass select mode, to facilitate easier moving of elements
• When stopping timeline, move to loop region start, if present, rather than start of timeline

Version 1.0.4

• Added support for Inter-App Audio effects and audio sources
• Added search fields to effect/audio source pickers
• Fixed some issues with using AUv3 effects as MIDI sources (like MIDI Guitar 2)

Version 1.0.3

• Added loop and one-shot time stretch settings
• Added support for APC40 mk2 features: shift key, modes for top knobs and device knobs
• Added bank select for APC40 mk2, for scrolling around clips
• Tweaked “Record” binding behaviour for Launchpad/APC40: Use “play if stopped” option only for taps (fixes record issues on double tap/hold)
• Increased max ramp duration for all “Mute” actions to 10 seconds
• Fixed some pops/crackles and audio drop-outs
• Fixed an issue with endlessly-flashing track controls
• Added fallback identification for MIDI Action targets, to work around an IDAM issue
• Fixed crash in “Mixer Solo” action configuration, when changing action
• Fixed some wacky play group outline rendering issues
• Fixed continuous Adjust Tempo actions
• Fixed issue with handling of incoming MIDI timestamps, affecting GeoShred and MIDI Guitar 2
• Fixed a number of memory leaks, particularly affecting LP when hosted as AUv3
• Fixed issue with lingering AU windows when deleting a MIDI source AU
• Fixed crash when recording two initial loops simultaneously

Version 1.0.2

• Implemented bus actions
• Fixed MIDI Learn for audio source gain
• Added ability to use impulse triggers bound to “Toggle” button widget actions
• Fixed an issue with “trigger widget” actions not showing feedback on load
• Fixed some issues with “trigger widget” actions bound to a global control profile
• Fixed an issue with some interfaces (eg. RME BabyFace Pro) not showing all available ins/outs
• Fixed relative CC detection issues
• Suspend AUv3 frame size changes while resizing windows
• Always start clock when starting record, unless “Auto End Detected Loops” is on

Version 1.0.1

• Added support for iOS 12 and 13
• Added MIDI clock receiving
• Fixed a crash when adding an FX AUv3 as a MIDI source
• Fixed track waveform update issue (e.g. after twisting loops)
• Fixed lost/stuck notes from some MIDI sequencers
• Fixed playback/solo configuration screen missing some configuration items in certain contexts
• A number of other crash fixes

Open the Loopy Pro roadmap below to view and vote on current roadmap items, suggest ideas and leave feedback, and subscribe to receive email notifications on when individual roadmap items are implemented.

Open Loopy Pro Roadmap